Skip to main content
Glama

pause_subscription

DestructiveIdempotent

Pause the authenticated user's posterly subscription for 30 days (one pause allowed per 90-day cooldown). A free trial cannot be paused (409 trial_not_pausable). Billing action; requires the billing:write scope. Only call after the user explicitly confirms.

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

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true after the user explicitly confirms pausing the subscription.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, and the description layers on real operational context: a 30-day pause length, a one-per-90-day cooldown rate limit, a specific 409 error case, and a required billing:write scope. That is exactly the kind of consequence-and-permission detail the agent cannot get from the structured fields.

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?

Three short sentences, front-loaded with the action and duration, then the constraint and error code, then the confirmation gate. Every clause carries an actionable fact with no 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 single-parameter mutation with no output schema, this covers duration, rate limits, scope requirements, the failure mode, and the human-in-the-loop gate. An agent has everything needed to decide and invoke correctly.

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?

There is one parameter at 100% schema coverage, so the schema already explains that confirm must be true. The description reinforces the confirmation workflow but adds no syntax or format meaning beyond what the schema states, so the baseline of 3 applies.

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

Purpose4/5

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

The description names a specific verb and resource ('Pause the authenticated user's posterly subscription') plus a concrete duration (30 days), which is far more than a restatement of the name. It does not explicitly route the agent away from near-neighbors like resume_subscription or manage_publishing_pause, so the sibling differentiation is only implicit.

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?

It gives clear preconditions: only call after the user explicitly confirms, and do not call on a free trial (409 trial_not_pausable). No alternative tools are named for the reverse or cancellation case, so it falls short of the explicit when/when-not/alternatives bar.

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