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?
Description discloses behavioral traits beyond annotations: ownership enforcement, deactivation (not deletion), and retention of historical events via recent_alerts. No contradiction with annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true).
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, no wasted words. Front-loaded with action, then key behavioral details. Every sentence earns its place.
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 param, no output schema), the description covers essential context: cancellation effect, ownership, and link to sibling tool recent_alerts. Slight omission of return format, but acceptable.
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 a clear schema description for 'id' (uuid from subscribe). The description adds minimal value beyond schema, only referencing 'by id' and ownership, which is already implied. Baseline 3 is appropriate.
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 uses a specific verb ('Cancel') and resource ('subscription') immediately, clearly stating the action. It distinguishes itself from siblings like 'subscribe' and 'list_subscriptions' by specifying cancellation.
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 states ownership enforcement ('you can only cancel your own subscriptions'), guiding the agent on when the tool applies. It does not list alternatives but provides sufficient context for correct invocation.
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 tools are near-duplicates (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded), and there are overlapping clusters among the polymarket_* tools, research tools (deep_research, entity_profile, compare_entities, recent_changes), and AI-visibility tools (ai_visibility_check vs scan_competitor_ai_presence). The detailed descriptions help, but an agent selecting among these could easily pick the wrong one.
Snake_case is used consistently, but the naming pattern is otherwise mixed: some tools are verb_noun (validate_claim, suggest_questions), some are bare nouns (entity_profile, polymarket_edges), some are verbs without objects (remember, forget, ask_pipeworx), and only the five QuickBooks tools share a qb_ prefix. This creates multiple naming ecosystems with no unified convention.
At 36 tools, this is well above the 25+ threshold for 'too many'. More importantly, the server is named Quickbooks but only 5 tools are accounting-related; the other 31 are unrelated Pipeworx data, prediction-market, memory, and meta tools, making the count both excessive and off-purpose.
For the QuickBooks domain named by the server, the surface is read-only: get customer, get invoice, list accounts, list invoices, and generic query. There are no create, update, delete, payment, bill, deposit, or report operations, which is a significant gap. For the broader Pipeworx data domain it is fairly complete, but that domain is not what the server name promises.