Skip to main content
Glama

Get a link to subscribe to a plan

create_plan_checkout

Returns a Stripe Checkout link where the user subscribes the connected account to a plan. Charges nothing by itself: give the link to the user to open and pay.

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

Input Schema

NameRequiredDescriptionDefault
planYesA plan key from list_plans.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already mark this as a non-destructive, open-world write, so the safety bar is covered. The description adds genuinely non-obvious behavior: no charge occurs on the call itself, and payment only happens when the user opens the link. The only missing piece is what the response looks like beyond 'a link' (expiry, error when the account is not connected).

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 sentences, no filler. The most important constraint (it returns a link rather than charging) is front-loaded in the first sentence and reinforced immediately in the second.

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 one-parameter tool with no output schema, the description covers what is returned and what does not happen, which is the essential context. It could still say how the link is delivered or whether it expires, but nothing needed to call the tool is missing.

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 a single parameter with 100% schema coverage, and the schema already says it is 'A plan key from list_plans.' The description adds no format, casing, or lookup detail beyond that, 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 uses a concrete verb and resource: it 'Returns a Stripe Checkout link where the user subscribes the connected account to a plan.' That is far more specific than the title alone and makes the deliverable (a link, not a charge) unmistakable. It stops short of naming a sibling such as create_balance_checkout to contrast with, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

It gives a usage flow ('give the link to the user to open and pay') and implicitly tells the agent this is a hand-off, not a completion. However, it never states when to choose this over create_balance_checkout or get_billing_portal_link, nor any prerequisite such as the account being connected. Usage is implied rather than delimited.

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