Your assistant now knows what a tool will do
Every one of the 71 tools now carries behaviour hints: whether it only reads, whether it's destructive, and whether running it twice is safe.
That changes the experience in a specific way. A host that reads these hints can auto-approve read-only calls — listing tasks, fetching a feature, pulling the product brain — so you stop clicking approve on things that can't change anything. And it can warn you properly before a destructive one, like deleting a task or merging two end users, instead of treating every call as equally risky.
Writes never masquerade as reads. That's asserted in the test suite, not just intended.
The same tools however you connect
There are several ways to connect: the hosted connector, the npm package, and the desktop extension. Until now they each described their tools separately, so keeping them identical was a rule someone had to remember.
The tool definitions now live in one registry that all of them build from. Parity isn't a discipline any more, it's structural — the surfaces can't drift apart, because there's only one source to drift from.
The npm and desktop surfaces pick up what only the hosted connector had: human-readable tool titles, worked examples, and the rich cards that render results as something you can read instead of raw JSON.
Better failures
The client used to assume every response was JSON, so a gateway returning an HTML error page produced a parser crash rather than a useful message. Requests now carry a 30-second timeout and report what actually came back.
Available now — npm @aioproductoscom/mcp 0.16.0. Existing connections pick up
the hints on reconnect; nothing to reconfigure.