Skip to main content
Glama

Start a checkout

start_checkout

[writes flayr data · write scope] Returns a checkout link for a plan from list_plans (interval monthly or annual, default monthly). A HUMAN opens it and pays: Stripe Checkout for individual plans, the organization set-up page for org plans, or the plan page when the account already has a card. This call never charges anything. Only call it when the user asks to upgrade. (Wraps POST /api/v2/billing/checkout.)

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": {
      "plan": "<plan>"
    },
    "name": "start_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesFormat: string; e.g. "Example". A plan id from list_plans (e.g. starter, pro).
intervalNoFormat: string; e.g. "monthly". Default monthly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / interval / description
      Previous value: -"Default monthly."New value: +"Format: string; e.g. \"monthly\". Default monthly."
    • changedInput schema / properties / plan / description
      Previous value: -"A plan id from list_plans (e.g. starter, pro)."New value: +"Format: string; e.g. \"Example\". A plan id from list_plans (e.g. starter, pro)."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only give the generic write/idempotent/destructive flags, and the description adds substantial context: this call never charges anything, a human must open and pay the link, the write scope is required, and which surface the link points to depends on account state. What remains unstated is whether the link expires or whether repeated calls create duplicate sessions.

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?

Content is front-loaded with the outcome first, then eligibility, then the never-charges caveat, which is the right order for a write tool. The trailing wrapper note about the POST endpoint is mild filler but does add implementation context.

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 no output schema, the description carries the return-value burden and does so (a checkout link) while explaining that the link, not this call, performs payment. Combined with annotations it tells an agent everything needed to call it safely and set user expectations.

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?

Schema coverage is 100% and the schema already documents both parameters, including the monthly/annual enum with its monthly default and the fact that plan ids come from list_plans. The description restates those facts without adding format, constraint, or failure-mode detail beyond the schema.

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?

"Returns a checkout link for a plan from list_plans" states a specific verb (returns) and resource (checkout link) plus the upstream dependency, and the parenthetical spells out the three concrete destinations (Stripe Checkout, org setup page, plan page). An agent can distinguish this from subscription_status or list_plans purely from the description.

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?

"Only call it when the user asks to upgrade" is an explicit gate on when to invoke, and the description names list_plans as the source of valid plan ids. It lacks a direct contrast with sibling tools (e.g. subscription_status for checking current state), so it stops short of full when/when-not guidance.

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