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 significant behavioral context beyond annotations: ownership enforcement and deactivation semantics (not deleted, historical events remain). Complements the annotations effectively.
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, no wasted words. Front-loaded with the main action, making it easy for an agent to parse quickly.
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 clear annotations, the description fully covers the purpose, constraints, and behavioral nuances. No gaps identified.
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 description does not add extra meaning beyond the schema's parameter description. Baseline of 3 is appropriate.
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 action ('Cancel a subscription by id'), specifying the verb and resource. Distinguishes 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?
States ownership enforcement ('you can only cancel your own subscriptions'), providing clear context on when to use. Does not explicitly mention alternatives, but the constraint is well understood.
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 clear distinct purposes, but the three ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) are very similar, and there is some overlap between bet_research and polymarket_edges. Overall, the majority are well-differentiated.
Tool names follow a consistent snake_case verb_noun pattern with only minor deviations (e.g., 'chokepoints_list' vs 'chokepoint_daily_traffic'). The naming convention is predictable and clear.
At 37 tools, the surface is overly large for a focused server. Many tools are meta-tools that could have been consolidated, and the count exceeds the recommended range (25+), making it feel heavy and unwieldy.
The server covers maritime chokepoints comprehensively (list, status, daily, compare, disruptions), and the Pipeworx-based tools provide broad coverage across financial, drug, prediction market, and general query domains. There are no obvious gaps for the stated scope.