Skip to main content
Glama

Cancel the paid plan

cancel_subscription
DestructiveIdempotent

Cancels the paid plan on the account that owns this API key, at the end of the period already paid for; it works until then and does not renew. Only when your user asks to cancel. A reason is required: Ask your user why they are cancelling. Do not guess or pick a reason for them. Send the matching reason id and their own words in comment (comment is required for reason "other"). Reasons: got_what_i_needed (I got the data I needed), too_expensive (Too expensive), missing_data (Missing data or features I need), reliability (Errors or slow responses), not_using (Not using it enough), switched (Switched to another service), other (Something else). Undo with keep_subscription. Costs no credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reason": "<reason>",
      "comment": "<comment>"
    },
    "name": "cancel_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy your user is cancelling, in their terms. Ask them; never guess.
commentYesYour user's own words about why, up to 500 characters. At least 3 characters when reason is "other"; send an empty string only if they gave nothing beyond the reason.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructive=true and idempotent=true, and the description adds substantive context on top: cancellation defers to the end of the paid period, service continues until then, no auto-renew, and it costs no credits. That is real operational information (effect timing, cost, reversibility) not derivable from the annotation flags.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The action, timing, and permission gate are front-loaded in the first two sentences, and the reason enumeration is functional rather than filler. The inline reason list duplicates the schema enum somewhat and makes the block dense, but nothing is truly wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two required params, no output schema, and annotations covering the safety profile, the description still supplies the pieces an agent would otherwise have to guess: billing timing, credit cost, reversibility via keep_subscription, and the required user-consultation step. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by spelling out each enum id with a plain-language gloss (e.g. got_what_i_needed = 'I got the data I needed') and by reinforcing that comment must carry the user's own words with the 'other' special case. Minor redundancy with the schema's 'other' rule, but it genuinely increases how confidently an agent can map user sentiment to an id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Cancels the paid plan'), plus the account scope ('the account that owns this API key') and timing ('at the end of the period already paid for'). An agent can distinguish this from keep_subscription and from other mutating tools without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit gate ('Only when your user asks to cancel') and names the reverse operation ('Undo with keep_subscription'). It also prescribes the conversational procedure — ask the user why, never guess or pick a reason — which is exactly the when/how guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources