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?
It adds important behavioral details beyond annotations: ownership enforcement and the deactivation (not deletion) behavior, ensuring the user knows historical events remain available. This complements the idempotentHint and destructiveHint 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?
The description is two concise sentences, front-loaded with the primary action, and every sentence provides useful context without redundancy.
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 explains the primary action, the ownership constraint, and the deactivation behavior. This is complete for an agent to invoke correctly.
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?
The input schema covers the sole parameter (id) fully, including its type and origin ('returned by subscribe'). The description does not add additional parameter semantics beyond that.
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 the action: 'Cancel a subscription by id.' It specifies the resource (subscription) and the operation (cancel), and distinguishes itself from related 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?
The description provides a clear usage context: you can only cancel your own subscriptions, which implies this tool is for the subscription owner. It doesn't explicitly mention alternatives, but the context 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.
ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical in purpose, and structure/summary both fetch PDB entries. The server name 'Rcsb Pdb' doesn't match most tools, which are Pipeworx data tools, compounding ambiguity.
Mostly snake_case verb_noun, but verbs are inconsistent (ask, discover, generate, list, recall) and some names are noun phrases (entity_profile, polymarket_edges). No clear pattern unifies the set.
37 tools is excessive for a server ostensibly about RCSB PDB; only 6 tools relate to PDB while 31 serve unrelated Pipeworx functionality. The count feels like a bundled grab-bag rather than a focused toolset.
The PDB-specific tools cover the core operations (search, fetch, assembly, ligand, polymer entity), so the structural biology surface is mostly complete. However, the server's overall purpose is muddled, and the Pipeworx tools are a separate domain that happens to be bundled in, making it unclear what 'completeness' even means for this server.