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?
The description adds context beyond annotations by clarifying that the row is deactivated (not deleted) and that ownership is enforced. This aligns with the non-destructive and read-only hints.
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 with zero waste. The first sentence immediately states the action, making it efficient and well-structured.
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?
Given the tool's simplicity (one parameter, no output schema), the description sufficiently covers the behavior and constraints. Could mention idempotency but annotation covers it.
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 description coverage is 100%, so the schema already documents the single parameter. The description does not add further parameter details, meeting baseline expectations.
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.' using a specific verb and resource. It distinguishes itself from sibling tools like 'subscribe' and 'list_subscriptions' by indicating it is the cancellation action.
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 explains ownership enforcement and the effect (deactivation, not deletion), but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. It implies usage context well.
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 tools have distinct purposes and the descriptions are unusually thorough, but ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and several discovery/prediction-market tools (polymarket_edges vs polymarket_arbitrage, discover_tools vs suggest_questions) occupy overlapping territory. An agent could reasonably route to the wrong variant despite the documentation.
The dominant convention is lowercase snake_case with a leading verb (ask_pipeworx, list_subscriptions, validate_claim, resolve_entity), which makes the set predictable. A few noun-first outliers like pipeworx_trending, recent_alerts, and polymarket_edge_tracker are minor deviations rather than a broken pattern.
34 tools is well above the coherence sweet spot for an MCP server, and much of that count is made up of meta-wrappers and convenience variants around the same Pipeworx router. The broad scope explains some of the count, but the surface still feels heavy for a single named server.
The Pipeworx side is very complete: lookups, grounded verification, research, entity profiles, comparisons, prediction-market fill checks, subscriptions, and memory all have lifecycle coverage. However, the server is named Obis and only find_occurrences, get_statistics, and get_taxon serve that domain, leaving obvious marine-biodiversity operations like occurrence detail, dataset listing, and download paths missing.