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?
Discloses that the row is deactivated (not deleted) and historical events remain via recent_alerts. Consistent with idempotentHint and adds 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 front-loaded sentences convey purpose, constraint, and side-effect without 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?
No output schema, but description fully covers behavior and side effects for a simple tool. Enough for correct invocation.
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 100% of parameters. Description clarifies that 'id' is the subscription id returned by subscribe, adding context beyond the 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 ('Cancel') and resource ('subscription') with specific identifier ('by id'). Distinct from sibling tools 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?
Explicit ownership constraint ('you can only cancel your own subscriptions') guides proper usage, though no direct comparison 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.
Most tools have distinct purposes, especially within the Polymarket and data query groups. However, the three ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and the overlap between deep_research and ask_pipeworx for broader questions could cause minor confusion.
Tool names follow some consistent prefixes (ask_pipeworx, polymarket_, scan_, recent_) but overall mix verb_noun, noun phrases, and standalone verbs (forget, recall, remember). This inconsistency reduces predictability, though the patterns are still readable.
32 tools is high but justifiable given the server's dual role as a Pipeworx data gateway and Polymarket analysis suite. Each tool serves a distinct function in the workflow, but the count borders on heavy and could be streamlined.
The tool set covers the full lifecycle for the server's domain: discovery, querying, grounded answers, entity resolution, company profiles, fact-checking, prediction market analysis, memory, and monitoring. Minor gaps exist (no account management or direct data modification), but these are out of scope for a read-only data interface.