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?
Annotations already indicate destructiveHint=false and idempotentHint=true. The description adds valuable context: 'The row is deactivated (not deleted) so its historical events stay available via recent_alerts.' This clarifies the non-destructive nature and persistence of data. No contradiction.
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 wasted words. Information is well-structured and easy to parse.
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 single-parameter mutation tool, the description covers purpose, ownership, side effects, and data persistence. No output schema is needed given the simplicity; the behavioral description is sufficient.
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 a clear description for param 'id'. The description only restates 'by id' without adding new semantics, so 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?
The description clearly states 'Cancel a subscription by id' with a specific verb and resource. It distinguishes from sibling tools like 'subscribe' (creates) and 'list_subscriptions' (reads).
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 ('only cancel your own subscriptions') and explains the deactivation behavior vs deletion, guiding when to use and what alternative tools like 'recent_alerts' are available for history.
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.
The three ask_pipeworx variants are near-identical (the beta is currently an exact copy of the stable router), and ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim all route natural-language questions to the same underlying source catalog. The six polymarket_* tools also heavily overlap in opportunity detection, though some clusters like memory and subscriptions are clearly separated.
The naming is mostly snake_case but mixes conventions: verb_noun (list_subscriptions, resolve_entity), noun-first (entity_profile, bet_research), metadata-style prefixes (pipeworx_trending, polymarket_edges), and bare verbs (remember, recall, forget). It is readable but does not follow one predictable pattern across the set.
33 tools is excessive for a server nominally named Open Notify, and the count is inflated by redundant ask_pipeworx variants and six closely-related Polymarket tools. The broad data-gateway scope could justify a large catalog, but the set feels bloated and unfocused rather than deliberately scaled.
For the apparent Open Notify domain, only astros and iss_now fit, and core ISS functionality like pass predictions is missing. The wider data-lookup surface is extensive, but the inclusion of unrelated memory, subscription, npm-scanning, and llms.txt tools means no single domain gets coherent lifecycle coverage.