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?
Even with annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description adds valuable details: ownership enforcement, row deactivation (not deletion), and preservation of historical events via recent_alerts. This meaningfully clarifies the tool's behavior.
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 sentences, front-loaded with the main action, and contains no filler or redundancy. Every sentence contributes useful detail.
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 fully covers the action, constraint, and side effects. The mention of recent_alerts also helps the agent understand the broader context.
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 the parameter id already described as 'Subscription id (uuid) returned by subscribe.' The description only echoes 'by id' and adds no new semantic information about the parameter, so the baseline 3 applies.
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' — a specific verb with a resource and method. It also distinguishes the tool's effect (deactivation rather than deletion) from related tools like 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?
Provides clear context for when to use (cancel a subscription you own) and mentions ownership enforcement. However, it does not explicitly contrast with sibling tools like subscribe or list_subscriptions, so it stops short of full alternative guidance.
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 have overlapping responsibilities: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded all serve similar lookup purposes. entity_profile, compare_entities, and recent_changes all retrieve company data. Several Polymarket tools overlap in edge detection. The large number of tools with fuzzy boundaries makes it difficult for an agent to select the correct one.
Tool names are a mix of conventions: some use verb_noun (lookup_postcode, validate_postcode, resolve_entity), others are verb_phrase (ask_pipeworx, deep_research, suggest_questions), and a few are compound (polymarket_arbitrage, scan_competitor_ai_presence). No uniform pattern, though the structure is readable.
Despite being named 'postcodes', only 4 of 35 tools are directly about postcodes. The vast majority belong to a broad data platform (Pipeworx) with specialized tools for finance, betting, news, etc. The count is excessive for a focused service, and many tools are only useful for users of that platform, leading to clutter.
For a postcode server, the tools cover basic needs (lookup, nearest, random, validate). However, the server's actual scope is much larger; within that broader scope, there are notable gaps: no general text search, no direct access to raw SEC filings, and many tools depend on paid plans or external accounts. The coverage is uneven and incomplete for a unified data platform.