Repository navigation
Conversation
…s that failed Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
In Axiom
zernio-mcp, a tool call FastMCP rejects for bad arguments logs aserror_type=ValidationError, the same name as an SDK model rejecting an API response. Since FastMCP 4.2.1 the log line no longer names the failing field either, so finding which argument broke (thenot_deletedandplatformbugs fixed in #116) meant digging through old Railway deployments. On FastMCP 4.2.1 a rejected response logs as_ToolBodyError, a private FastMCP class, with no field either.Fix
_error_fieldswalks the cause chain to the pydantic error:ValidationErrorlogserror_type: "InvalidArguments".error_type: "ValidationError".invalid_fields, e.g.status:literal_error,limit:int_parsing: field paths and error types only, never values (errors(include_input=False)), since arguments can carry customer content.Sentry is unchanged: argument errors stay expected failures, response rejections stay issues.
Validation
pytest tests/test_mcp_telemetry.py: 36 passed, 2 new (argument fields logged without the value; response rejection staysValidationErrorwith its field).pytest tests -k mcp: 1715 passed, 5 skipped. ruff and mypy clean.After deploy,
['zernio-mcp'] | where error_type == 'InvalidArguments' | summarize count() by tool, invalid_fieldsshows which arguments agents get wrong.🤖 Generated with Claude Code