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 indicate idempotentHint=true and destructiveHint=false. The description adds context that the row is deactivated (not deleted) and historical events stay available, which clarifies the non-destructive mutation behavior beyond the 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?
Two sentences with zero fluff. First sentence states the action, second adds constraints and side effects. 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?
For a simple tool with one parameter and no output schema, the description covers the action, ownership constraint, row status, and mentions related tool (recent_alerts). Complete and informative.
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 for 'id' already explaining it's a uuid from subscribe. The description does not add further parameter meaning.
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') and the resource (subscription identified by id). It differentiates from siblings 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 explicitly mentions ownership enforcement ('you can only cancel your own subscriptions'), which provides a clear usage constraint. However, it does not explicitly state when not to use or compare to alternatives.
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.
Several clusters blur together: ask_pipeworx, ask_pipeworx_beta (explicitly identical today), and ask_pipeworx_grounded share routing, while discover_tools/suggest_questions and the Polymarket edge/arbitrage/fill-risk tools have overlapping discovery purposes. Rich descriptions reduce some confusion, but an agent must read carefully to avoid misselection.
Most names are lowercase snake_case, but there is no consistent verb_noun pattern: ask_pipeworx/beta/grounded and polymarket_* are domain-prefixed, entity_profile/recent_changes are noun phrases, and query/metadata/remember are bare verbs or nouns. The naming is still readable and subfamilies share prefixes, so it is mixed rather than chaotic.
34 tools is above the comfortable range for a single MCP server, and several could be folded together (the beta variant, visibility checks, and Polymarket scanners). The breadth reflects a large platform, but the surface feels heavy for an agent to select from confidently.
The query side is strong: PA Open Data has datasets/metadata/query coverage, and Pipeworx provides ask, deep_research, entity_profile, compare, recent_changes, validate_claim, plus subscriptions and memory with lifecycle coverage. Minor gaps: descriptions promise resolvable pipeworx:// citations but no resource/read tool is exposed, and there is no direct way to fetch an arbitrary record by citation.