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 mutation behavior (deactivated, not deleted) and links to historical availability via recent_alerts, adding value beyond 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, front-loaded key action, no wasted words.
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 single-param mutation tool with annotations and clear behavioral notes.
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 covers parameter fully; description adds context that id comes from subscribe, but no extra syntax or format details needed.
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?
Clearly states 'Cancel a subscription by id' with specific verb and resource, and distinguishes 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?
Explicitly mentions ownership enforcement ('you can only cancel your own subscriptions'), guiding proper usage, though no explicit alternatives listed.
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 purposes (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded all serve similar query routing). Tools from unrelated domains (UK Gazette, Polymarket betting, AI visibility checks) are mixed together, making it hard for an agent to distinguish which tool to use for a given task.
Naming is chaotic: some tools use descriptive phrases with underscores (gazette_deceased_estates, polymarket_arbitrage), others use generic verbs (remember, recall, forget), and some include version or mode indicators (ask_pipeworx_beta, scan_competitor_ai_presence). No consistent pattern across the set.
With 36 tools, the server is overstuffed for its purported focus on the UK Gazette. The majority of tools (Polymarket, Pipeworx general, AI visibility, etc.) are unrelated to the server's name, making it feel like a bundling of many services into one, which is excessive for a coherent tool set.
For a server named 'Uk Gazette', there are only a handful of Gazette-specific tools (gazette_search_notices, gazette_insolvency_notices, etc.), while the rest cover unrelated domains. This leaves obvious gaps for Gazette-related tasks (e.g., no tool for searching particular notice types or filtering by edition), despite the large tool count.