Skip to content

fix(cli): treat MCP tool isError as a failed mcp call - #128

Open
Arshgill01 wants to merge 1 commit into
CALLE-AI:mainfrom
Arshgill01:fix/mcp-call-tool-error
Open

fix(cli): treat MCP tool isError as a failed mcp call#128
Arshgill01 wants to merge 1 commit into
CALLE-AI:mainfrom
Arshgill01:fix/mcp-call-tool-error

Conversation

@Arshgill01

Copy link
Copy Markdown

Summary

  • Generic calle mcp call treated any HTTP 200 MCP tool result as success, including isError: true, so it printed ok: true and exited 0.
  • Dedicated calle call * already throws CallStageError in that case. mcp call now uses the same check and safe remote-error fields.
  • Docs now say a JSON-RPC 200 is not tool success, and a successful status lookup is not a successful telephone call.

Fixes #127.

Test plan

  • pnpm --filter @call-e/cli test:unit — 61 pass, including mcp call treats tool isError as a failed command
  • Existing mcp call success tests still exit 0
  • pnpm --filter @call-e/cli check
  • pnpm --filter @call-e/cli pack:dry-run
  • Reviewer: fixture with HTTP 200 + result.isError: true should now match calle call status (ok: false, exit 1) and must not print extra structured secrets

Made with Cursor

Generic `calle mcp call` reported ok:true and exited 0 when the tool
result had isError:true. Use the same CallStageError path as dedicated
call commands so shell automation cannot take the success branch.

Closes CALLE-AI#127

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CLI: generic mcp call exits 0 for isError:true tool results

1 participant