Skip to main content
Glama

Checkout link

get_checkout_link
Idempotent

Checkout URL for a plan. With no arguments: the main paid plan. Where the site supports it the URL is a Stripe-hosted Checkout session (created unpaid; a human pays, nothing is charged by this tool). A free plan is only returned when the plan is requested or the company sells nothing else.

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

Input Schema

NameRequiredDescriptionDefault
planNoplan name from list_pricing
intervalNo
buyer_emailNoonly for sites that need the buyer's email or store handle before checkout: the human buyer's own receipt email
accept_termsNoONLY where the site requires the buyer to accept its Terms/refund policy before checkout: set true only after the human buyer has read and accepted the policy links the tool lists. Never set it on your own.
store_handleNoonly where the site asks for it (StoreForge): the store handle the buyer chose, 3+ chars a-z 0-9 -

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / accept_terms
      Added value: +{
      +  "description": "ONLY where the site requires the buyer to accept its Terms/refund policy before checkout: set true only after the human buyer has read and accepted the policy links the tool lists. Never set it on your own.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / buyer_email
      Added value: +{
      +  "description": "only for sites that need the buyer's email or store handle before checkout: the human buyer's own receipt email",
      +  "type": "string"
      +}
    • addedInput schema / properties / store_handle
      Added value: +{
      +  "description": "only where the site asks for it (StoreForge): the store handle the buyer chose, 3+ chars a-z 0-9 -",
      +  "type": "string"
      +}
  2. Added
  3. Removed
  4. Added

TDQS

A3.9/5.0
Behavior4/5

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

Adds genuinely non-obvious context beyond annotations: the URL is a Stripe-hosted Checkout session "created unpaid; a human pays, nothing is charged by this tool" — which explains why readOnlyHint=false yet destructiveHint=false. It does not cover link expiry, reuse across buyers, or behavior when the plan name is invalid.

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?

Three sentences, front-loaded with purpose then default behavior, with no filler. The final sentence about free plans is slightly convoluted but still short and informative.

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?

No output schema exists, and the description compensates by describing the return value as a Stripe-hosted Checkout URL created in an unpaid state. For a 5-parameter, non-mutating-of-money tool this is nearly complete, missing only error/failure behavior.

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 80%, so the schema carries most parameter meaning, including detailed guidance for buyer_email, accept_terms, and store_handle. The description only adds the plan-level rule about free plans and the no-argument default, leaving interval and the other optional params unaddressed.

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?

States a specific resource ("Checkout URL for a plan") and immediately defines the zero-argument default ("the main paid plan"), so the agent knows both what is returned and what happens with no input. It does not explicitly contrast itself with siblings, though the schema's reference to list_pricing partly covers that routing.

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?

Gives clear conditional guidance: omit arguments to get the main paid plan, request a plan explicitly for other tiers, and it explains the free-plan fallback rule ("only returned when the plan is requested or the company sells nothing else"). It stops short of stating when NOT to use this tool or explicitly instructing the agent to call list_pricing first.

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