Max Isbey
ab89da82ba
A tool that crashed used to send the exception's own text to the client as "Error executing tool <name>: <str(exc)>". That text can describe server internals (or, for an output-schema failure, echo the tool's return value), so a crash now reads just "Error executing tool <name>". ToolError, ResourceError, and argument-validation messages still reach the model unchanged, since those are the anticipated failures it can act on. Closes the tool half of the leak that resources already avoided and that prompts stopped doing earlier in this branch. Related tidy-ups in the same direction: - a crashing @mcp.completion() handler is logged once and answered with -32603 "Error completing argument <name>" instead of str(exc) - the legacy resolver path reports a malformed elicitation answer as a ToolError, matching what the input_required path already did - the INFO line for rejected arguments names the fields, not the values Docs now teach ToolError as the way to talk to the model and describe a plain exception as a crash the model sees generically; examples that relied on ValueError text reaching the client raise ToolError instead.
23 lines
628 B
Python
23 lines
628 B
Python
from mcp.server import MCPServer
|
|
from mcp.server.mcpserver.exceptions import ResourceNotFoundError, ToolError
|
|
|
|
mcp = MCPServer("Weather")
|
|
|
|
FORECASTS = {"London": "Rain.", "Cairo": "Sun."}
|
|
|
|
|
|
@mcp.tool()
|
|
def forecast(city: str) -> str:
|
|
"""Today's forecast for one city."""
|
|
if city not in FORECASTS:
|
|
raise ToolError(f"No forecast for {city!r}.")
|
|
return FORECASTS[city]
|
|
|
|
|
|
@mcp.resource("weather://{city}")
|
|
def report(city: str) -> str:
|
|
"""The full report for one city."""
|
|
if city not in FORECASTS:
|
|
raise ResourceNotFoundError(f"No forecast for {city!r}.")
|
|
return f"{city}: {FORECASTS[city]}"
|