Skip to main content
Glama

Undo a scheduled cancellation

keep_subscription
Idempotent

Undoes a cancellation scheduled with cancel_subscription (or the account page), so the paid plan renews as usual. Only when your user asks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "keep_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, idempotent mutation; the description adds the meaningful behavior beyond them: it reverses a prior cancellation and restores automatic renewal. It still omits what happens when no cancellation exists or whether any confirmation/authorization step is required.

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

Conciseness5/5

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

Two short sentences, front-loaded with the effect and followed by the qualifying condition; every clause carries information an agent needs to decide on and interpret the call.

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

Completeness4/5

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

For a zero-parameter tool with annotations covering safety and idempotency and no output schema, the definition supplies purpose, precondition, and outcome. Only the no-op/error case (no cancellation pending) is left unspecified.

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?

The tool takes zero parameters, so there is no parameter meaning to convey; the description correctly implies the target is determined implicitly from the caller's own subscription. Baseline 4 applies for a parameterless tool, with no added parameter context needed.

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 ('Undoes') and resource ('a cancellation scheduled with cancel_subscription') plus the resulting state ('the paid plan renews as usual'). It clearly distinguishes itself from the sibling cancel_subscription, which schedules the cancellation this tool reverses.

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

Usage Guidelines4/5

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

Gives an explicit gating condition, 'Only when your user asks,' which implies when not to invoke it autonomously, and names the counterpart tool cancel_subscription (plus the account page) as the source of the state being undone. It does not spell out what to do if no cancellation is scheduled, so guidance is clear but not exhaustive.

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