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?
Discloses behavioral traits beyond annotations: ownership enforcement, deactivation vs deletion, and that historical events remain accessible via recent_alerts. No contradictions 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 sentences, front-loaded with action, no superfluous words. Every sentence adds value.
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 tool with one parameter and no output schema, the description fully covers purpose, behavioral effects, and side effects. 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 covers the single 'id' parameter with description; the description adds that it's the id returned by subscribe, providing useful context beyond schema.
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 'Cancel a subscription by id', identifying the specific verb (cancel) and resource (subscription), and it 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?
Specifies ownership enforcement and that the row is deactivated not deleted, providing clear context for when to use and what to expect. Could be more explicit about when not to use, but still gives strong guidance.
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.
Multiple tools overlap significantly: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded serve nearly identical purposes, and deep_research further duplicates. Polymarket tools (bet_research, polymarket_arbitrage, polymarket_edges, etc.) also have overlapping scopes, making it hard for an agent to select the correct one without deep inspection.
Tool names use a mix of patterns: some are descriptive phrases (ai_visibility_check, generate_llms_txt), others are domain-prefixed (nz_tender_*, polymarket_*) but lack a uniform verb_noun structure. The ask_pipeworx series diverges from the rest, and verb choices are inconsistent (compare_entities vs scan_competitor_ai_presence).
With 34 tools, the surface is large and feels bloated. The server covers multiple distinct domains (NZ tenders, Polymarket, memory, subscriptions) that could be separate servers. Many tools are variants of the same core functionality (e.g., four ask_pipeworx variants), inflating the count without clear necessity.
For a general-purpose data query server, the tool set covers a broad range of sources (SEC, FDA, FRED, etc.) and includes CRUD for memory and subscriptions. However, obvious gaps exist: no dedicated web search tool (ask_pipeworx is for structured data), and NZ coverage is limited to tenders only. Missing update/delete for some resources (e.g., no way to modify a subscription beyond unsubscribe).