unsubscribeCancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Subscription id (uuid) returned by subscribe. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations (idempotent, non-destructive, readOnlyHint false), the description adds critical behavioral details: ownership enforcement and soft-delete semantics. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two succinct sentences with no redundancies. The key action and constraints are front-loaded, making it highly scannable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with annotations, the description fully covers purpose, ownership, and post-action state. No output schema, but not needed given the context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single parameter 'id' is fully described in the schema. The description does not add additional parameter-specific meaning beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Cancel a subscription by id') and immediately specifies the resource and ownership constraint. Distinguishes well from sibling 'subscribe' by being its inverse.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly tells when to use (own subscriptions) and what happens (deactivation, not deletion). Though no alternative tools are mentioned, the context is clear enough for an agent to decide.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tool families heavily overlap: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve 'find/query Pipeworx data' with blurry boundaries, and the six Polymarket tools (bet_research, polymarket_edges, polymarket_edge_tracker, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread) have overlapping purposes. An agent could easily pick the wrong one without reading every description.
Most tools follow snake_case verb_noun patterns (list_dataflows, get_data, compare_entities, resolve_entity), and families share prefixes (pipeworx_*, polymarket_*, ask_pipeworx_*). However, the server is named 'Unicef' while almost all tool names reference Pipeworx/Polymarket, and verb choices vary widely, so the overall set lacks a unified naming story.
34 tools is already on the high side, but the real problem is scope: only 3 tools (list_dataflows, dataflow_structure, get_data) relate to the server's stated UNICEF purpose, while the other 31 are an unrelated grab bag of Pipeworx research, prediction-market betting, memory utilities, npm scanning, and llms.txt generation. This is a severe mismatch between count and purpose.
For the UNICEF domain implied by the server name, the surface is minimal: browse, structure, and fetch data cover read-only access but nothing else, and the overwhelming majority of tools are off-domain. If the inferred domain is instead 'Pipeworx + prediction markets', coverage is broad, but then the server name is fundamentally misleading and the UNICEF subset is an incomplete afterthought.