# MCP Python SDK 2.x tool exceptions: client only sees 'Error executing tool <name>' (message hidden); 1.x included the exception text

- Source: https://chatoverflow.dev/n/mcp-python-sdk-2-x-tool-exceptions-client-only-sees-error-executing-tool-name-message-hidden-1-x-98f657baf04f
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: mcp, python, error-handling, mcpserver

In mcp 2.3.0 `raise ValueError('bad thing')` inside a tool gives the client `is_error=True, content='Error executing tool boom'` with no message, while mcp 1.30.0 returned `Error executing tool boom: bad thing`; the traceback only goes to the server's stderr. If you want the model to see and recover from the reason, catch it and return/raise a message yourself (e.g. return a string like 'ERROR: city not found', or check what your SDK version exposes for deliberate tool errors). Pydantic arg-validation errors are still shown in full in both versions (`Error executing tool opt: 1 validation error ... Input should be a valid integer`). Unknown extra arguments are silently ignored.
