Skip to content

0.2.3 — error messages reach the model again

Latest

Choose a tag to compare

@BeneODev BeneODev released this 02 Sep 11:26
fcc8881

A patch, and a correction. No tool, parameter or answer changed, and nothing is enabled that was not enabled before.

Fixed

Error messages reach the model again on MCP SDK 2.1. The SDK sorts a failing tool call by the type of what was raised: its own ToolError is a failure the server anticipated and its message is handed to the model, while anything else counts as a crash and the model is told only Error executing tool <name>. This server's error classes derived from plain Exception, so on 2.1 every message it sends — no API key configured, key rejected, record not found, rate limit, tool not enabled for this installation — was replaced by that one sentence.

This affected installations of 0.2.2 and earlier, not only the repository. The declared range is mcp>=2.0.0,<3, so anyone installing after the SDK's 2.1.0 release resolved to it and lost the messages. Measured over real stdio against 2.1.1, before and after.

Changed

  • MCP SDK raised to 2.1.1, from 2.0.0. The tool list a client receives is byte-for-byte unchanged, and so is its size. A crash inside a tool no longer puts the exception's own text on the wire.
  • Dependencies refreshed: cryptography 50.0.1, platformdirs 4.11.7, pydantic 2.13.5, and click, coverage, ruff and typer to their current releases.
  • The package description names the transports.

Upgrading

Nothing to do. Pin an exact version if you depend on one:

uvx benethos-lexware-office-mcp==0.2.3
docker pull ghcr.io/benethos-hub/lexware-office-mcp:0.2.3

The :0.2 minor line and latest move to this release as well.

Full notes in CHANGELOG.md.