v0.3 JSON-RPC returns -32600 instead of -32602 for invalid params #1417

Activity

1. github-actions

   assigned

   mykytanetipa

   and

   rohityan

   on Nov 3, 2026
2. rohityan

   unassigned

   mykytanetipa

   on Nov 3, 2026
3. rohityan

   added

   component: serverIssues related to frameworks for agent execution, HTTP/event handling, database persistence logic.Issues related to frameworks for agent execution, HTTP/event handling, database persistence logic.

   on Nov 3, 2026
4. rohityan

   added the

   Bug

   issue type on Nov 3, 2026
5. rohityan commented on Nov 3, 2026

   

   rohityan

   on Nov 3, 2026

   More actions

   Hi @ConnorMoss02, thanks for reporting this!

   You correctly identified the root cause in JSONRPC03Adapter.handle_request. Schema validation failures on method parameters should emit -32602 (Invalid params) rather than -32600 (Invalid Request), aligning with both JSON-RPC 2.0 specifications and the v1.0 dispatcher behavior.

   The fix and test coverage in PR #1419 look solid. I have assigned this issue to you while the PR goes through review and merge. Thanks for contributing!
6. rohityan

   assigned

   ConnorMoss02

   and unassigned

   rohityan

   on Nov 3, 2026
7. rohityan

   added

   status:awaiting response

   component: serverIssues related to frameworks for agent execution, HTTP/event handling, database persistence logic.Issues related to frameworks for agent execution, HTTP/event handling, database persistence logic.

   and removed

   component: serverIssues related to frameworks for agent execution, HTTP/event handling, database persistence logic.Issues related to frameworks for agent execution, HTTP/event handling, database persistence logic.

   on Nov 3, 2026