Skip to main content
Glama

samgovapi.io

cancel_subscription

Cancel your user's paid plan at the end of the current billing period. Only call this when your user asked to cancel. A reason is required: ask your user why they are cancelling and pass their answer; never pick a reason for them. 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). "other" needs a comment. keep_subscription undoes it. Costs no quota.

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>"
    },
    "name": "cancel_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientNoYour name, such as Claude Code or Cursor.
reasonYesWhy your user is cancelling, in their words mapped to one id. Ask them; never guess.
commentNoYour user's own words about why. Required when reason is other.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the deferred effective date (end of billing period), reversibility via keep_subscription, and that the call costs no quota. It does not state permission/scope requirements or what the response contains, which keeps it short of a 5.

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?

Front-loads the action and timing, then the gating rule, then the reason taxonomy. The enum list is somewhat redundant with the schema's own enum, but each sentence still carries a distinct instruction; nothing is filler.

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?

For a 3-parameter mutation with no annotations and no output schema, the description supplies everything an agent needs: timing of effect, reversibility, cost, user-consent requirement, and full reason semantics. No important behavior is left to inference.

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 already 100%, so the baseline is 3; the description earns extra by glossing every enum id in plain language (got_what_i_needed, too_expensive, etc.) and flagging that 'other' requires a comment. It still doesn't explain the 'client' parameter's purpose beyond what the schema says.

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 ('Cancel your user's paid plan') and adds the crucial timing qualifier 'at the end of the current billing period', which distinguishes it from an immediate termination. An agent can tell instantly what this does.

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 gating condition ('Only call this when your user asked to cancel') and names the reversal path ('keep_subscription undoes it'), so both the when and the when-not are covered. It also instructs the agent to ask the user for a reason rather than infer one, which is a usage rule not recoverable from the schema.

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