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 that the row is deactivated not deleted, aligning with destructiveHint=false; ownership enforcement is additional context beyond 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?
Three sentences, all essential, front-loaded purpose, no redundant information.
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?
Complete given simple input schema and no output schema; covers ownership, soft delete, and historical events.
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 already fully documents the single parameter with description; description adds no new parameter detail, baseline of 3 applies.
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?
Clearly states verb 'Cancel' and resource 'subscription', and 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?
Explicitly states ownership enforcement and that only own subscriptions can be canceled, also describes the soft-delete behavior and preservation of historical events.
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 have unclear boundaries: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicates (the beta is currently identical), and the six polymarket_* tools plus bet_research heavily overlap in prediction-market analysis. ai_visibility_check and scan_competitor_ai_presence also serve the same core function. An agent would frequently need to read lengthy descriptions to pick the right one, and could easily misselect.
Most tools follow a readable snake_case pattern, but the style is mixed: some are verb-first (ask_pipeworx, search_datasets, resolve_entity), some are domain-prefixed nouns (polymarket_edges, pipeworx_feedback), and a few are bare nouns or adjective-noun phrases (dataset, entity_profile, recent_alerts). It is not chaotic, but there is no single predictable verb_noun convention across the set.
With 34 tools, this is above the 25+ threshold considered too many for a coherent toolset. The count is inflated by near-duplicate families (three ask_pipeworx variants, six polymarket tools) that could reasonably be consolidated. While the server covers a broad domain, the number of top-level choices creates unnecessary selection burden for agents.
For a read-focused data/research gateway, the surface is quite complete: general lookup, grounded verification, deep research, entity resolution, comparisons, change tracking, memory, subscriptions, and feedback are all present. Minor gaps exist, such as no direct fetch-by-URI tool for the pipeworx:// citations that other tools return, and the Dutch open-data tools are strictly read-only. These are workarounds rather than dead ends.