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. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that the row is deactivated (not deleted) and historical events remain available via recent_alerts. Adds context beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true).
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, front-loaded with action, no wasted words. Efficiently communicates purpose, constraints, and behavior.
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 for a simple tool with one parameter and no output schema. Covers purpose, usage constraint, behavioral nuance, and implications for historical data.
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 clear description of the 'id' parameter. Description adds ownership enforcement but does not provide additional parameter details 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?
Clear verb+resource: 'Cancel a subscription by id.' Distinguishes from sibling tools like 'subscribe' (create) and 'list_subscriptions' (view).
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?
States ownership enforcement ('you can only cancel your own subscriptions'), which guides when to use. No explicit alternatives or 'when not to use', but purpose is distinct enough.
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.
Most clusters have clear roles, and the detailed routing guidance separates ask_pipeworx from deep_research and grounded mode. However, three ask_pipeworx variants (one currently identical to stable), plus overlapping opportunity-discovery tools (polymarket_edges vs bet_research) and discovery/onboarding tools (discover_tools vs suggest_questions), leave several boundary cases where an agent could select the wrong tool.
Many tools group under readable prefixes (ask_pipeworx, cambridge_, polymarket_, pipeworx_) and are mostly snake_case. But the set mixes bare verbs (remember, recall, forget), verb_noun actions (resolve_entity, validate_claim), and noun-phrase names (entity_profile, recent_changes, polymarket_fill_risk), so no single convention predicts the full API.
34 tools is well into the 'too many' band, and the count is inflated by a kitchen-sink mix of data querying, prediction-market analysis, memory, subscriptions, feedback, llms.txt generation, and npm scanning. The server name 'Data Cambridge' suggests a narrow local-data scope, which makes the sprawl look even less appropriate.
Individual verticals are fairly complete: query/grounded/beta router levels, entity resolution/profile/compare/change, prediction-market discovery through fill-risk, and full memory and subscription CRUD. The major gap is discover_tools, which returns tools promoted as ready to call directly but no generic invocation tool is exposed, so the agent must route back through ask_pipeworx.