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 ownership enforcement and deactivation behavior beyond annotations. Annotations already indicate non-destructive and idempotent; description adds context that historical events remain available and links to 'recent_alerts'.
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. Action is front-loaded. Every sentence adds meaningful 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?
For a simple tool with one parameter and no output schema, the description covers ownership, idempotency, deactivation, and data retention. No gaps for agent usage.
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 description of 'id' parameter. Description adds value by clarifying that the id is 'returned by subscribe', providing useful linkage. Avoids redundancy.
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 'cancel a subscription by id' with specific verb and resource. It distinguishes from deletion by noting 'deactivated (not deleted)' and references sibling tools like 'subscribe' and 'recent_alerts'.
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 ('you can only cancel your own subscriptions') and explains the deactivation behavior, but does not explicitly contrast with alternatives like 'unsubscribe' vs 'delete' (though no delete tool exists). Guidance is sufficient.
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.
Many tools overlap in purpose: ask_pipeworx, ask_pipeworx_grounded, ask_pipeworx_beta, and deep_research all perform similar data lookups with slight variations. Prediction market tools (bet_research, polymarket_arbitrage, polymarket_edges) also overlap. Only the three PDBe-specific tools are clearly distinct, but overall the set is confusing.
Tool names follow no consistent pattern: some are verb_noun (ask_pipeworx, get_molecules), others are noun_verb (ai_visibility_check), or have mixed conventions (generate_llms_txt, uniprot_mappings). The variety of verbs (ask, bet, compare, discover, generate, get, list, recall, remember) makes it hard to predict tool names.
With 34 tools, the server is overstuffed for a single domain. It mixes PDBe-specific tools (3) with a large set of general-purpose data tools, prediction market tools, subscriptions, and memory tools. This bloat suggests the server should be split into focused services.
For the stated PDBe domain, only three tools exist (get_molecules, get_summary, uniprot_mappings), missing essential operations like search, download, or advanced queries. The server's overall purpose is unclear, and it feels like a random collection of tools rather than a coherent API.