Skip to main content
Glama

pause_subscription

Mark an active manual subscription as past_due. Provider-backed subscriptions cannot be paused here — cancel them or manage them at the payment provider.

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": {
      "subscriptionId": "<subscriptionId>"
    },
    "name": "pause_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscriptionIdYesSubscription ID

Output Schema

NameRequiredDescriptionDefault
dataYesTool result payload — shape varies per tool, see the tool description
summaryYesOne-line human-readable summary of the action
renderTypeYesUI rendering hint for the result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive, not idempotent), so the bar is lower, and the description still adds real semantics: the resulting state is specifically 'past_due', not a generic 'paused' flag, and eligibility is restricted to manual subscriptions. It does not mention reversibility (e.g. resume_subscription) or permission requirements, which is a modest gap.

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 with zero filler; the action and the resulting state are front-loaded, and the eligibility caveat follows immediately after. Nothing repeats the tool name or title.

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 single-parameter mutation with an output schema, the definition covers what changes (status becomes past_due) and who is eligible. What it omits is the recovery path and any permission/precondition detail beyond 'active manual subscription', a minor gap given the annotations carry safety signals.

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

Parameters3/5

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

Only one parameter, and schema description coverage is 100%, so the schema already documents subscriptionId fully. The description adds no format, source, or format constraints for the ID, so the baseline 3 applies.

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?

Names a specific verb ('Mark ... as past_due') and resource (subscription), and immediately delimits the eligible set to 'active manual subscription'. The second sentence separates it from the provider-managed case and points at cancel/manage-at-provider, so the agent can distinguish it from cancel_subscription and resume_subscription without opening either schema.

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?

Provides a clear when-not condition ('Provider-backed subscriptions cannot be paused here') and redirects to cancel or the payment provider. The when-to-use case is implied by 'active manual subscription' rather than stated as a positive trigger, and sibling tool names are not cited explicitly, keeping it just short of a 5.

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.