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?
Adds value beyond annotations: ownership enforcement, deactivation vs deletion, and linkage to 'recent_alerts'. Annotations already indicate non-destructive and idempotent.
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 sentences, front-loaded with main action, no unnecessary words.
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?
Simple tool with one parameter and no output schema; description covers behavior, ownership, and outcome, making it complete.
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% with clear description of 'id' parameter; description adds no further semantics beyond what 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?
Description clearly states the verb 'cancel' and resource 'subscription by id', distinguishing it from sibling tools like 'subscribe' and 'list_subscriptions'.
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 states ownership enforcement and explains that deactivation preserves historical events via 'recent_alerts', providing context on when to use. Could mention alternatives more directly.
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.
Most tools have clearly distinct purposes, but the multiple 'ask' variants (ask_pipeworx, ask_pipeworx_grounded, deep_research) and discovery tools (discover_tools, suggest_questions) could cause confusion. Descriptions help differentiate, but the overlap is notable.
All tool names use lowercase with underscores, but there is a mix of verb-first (e.g., ask_pipeworx, fetch_indicator) and noun-first (e.g., ai_visibility_check, polymarket_arbitrage) patterns. Consistent style but varied structure.
33 tools is excessive for a coherent set. The server covers diverse domains (data lookup, betting, memory, subscriptions, web generation, package scanning) without a clear unifying theme, making it feel like a collection of utilities rather than a focused tool surface.
Core data retrieval and research capabilities are well-covered, but there are notable gaps such as lack of data update tools for OWID and no direct visualization. Additionally, the betting tools are extensive while other areas like entity editing are missing.