Skip to main content
Glama

Account: Start subscription

account_start_subscription

Return Stripe Checkout links (one-click hosted payment, no need to visit the website) to start or restore the paid subscription when the user is on trial, the trial expired or the subscription lapsed. Use after a subscribe result or when the user asks to subscribe/pay/upgrade before having a subscription. If the user already has an active Stripe subscription, use account_change_plan instead. Present monthly and annual options; default to the current plan unless the user chose another one.

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": "account_start_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoTarget plan: personal (1 account per provider), personal_plus (up to 10 accounts, several per provider allowed) or team (5 isolated users, extra seats available).
intervalNoBilling interval. Annual = 10 monthly payments (2 months free). Defaults to the user's current interval.

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?

Annotations declare a non-read-only, non-destructive, non-idempotent call, and the description adds the crucial nuance that it produces one-click hosted Checkout links rather than charging directly — payment happens on Stripe's side. It does not mention what the link payload looks like (expiry, whether multiple links are returned per interval) or any rate limits, which keeps it below 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?

The most important fact — that it returns Checkout links — is front-loaded, followed by trigger conditions, the alternative tool, and presentation guidance. Every sentence carries distinct information, though the first sentence is dense and the parenthetical 'no need to visit the website' is slightly ambiguous rather than clarifying.

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 fully documented enum parameters, no output schema, and annotations covering the safety profile, the description supplies exactly the missing pieces: the return artifact (links), the trigger states, the alternative tool, and defaulting behavior. Nothing needed to invoke it correctly is absent.

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 would be 3, but the description adds caller-facing guidance not present in the schema: present both monthly and annual options, and default to the current plan unless the user chose otherwise. That default rule for 'plan' goes beyond the schema, which only documents the interval default.

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?

The description opens with a specific verb and artifact — 'Return Stripe Checkout links' — plus the exact account states that qualify (trial, expired trial, lapsed). It also names the sibling it must not be confused with (account_change_plan), so an agent can distinguish it without reading schemas.

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?

It gives an explicit trigger ('Use after a subscribe result or when the user asks to subscribe/pay/upgrade'), a precondition ('before having a subscription'), and a clear exclusion routing to account_change_plan for users with an active Stripe subscription. Both when-to-use and when-not-to-use are covered.

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.