Skip to main content
Glama

Get a checkout link

get_checkout_link
Read-only

Get the Dodo Payments checkout link for one RankRoot plan, to hand to the user. The user pays on Dodo Payments and receives a license key by email; pass it as 'Authorization: Bearer ' for higher API/MCP limits. If checkoutOpen is false, the plan is not on sale yet: the link is its pricing card where the user can join the waitlist.

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

Input Schema

NameRequiredDescriptionDefault
planYespass (Launch Kit, $79 once), tracker_m ($29/month) or tracker_y ($290/year) (Growth Tracker), employee_m ($149/month) or employee_y ($1490/year) (Growth Employee, done for you)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / plan / description
      Previous value: -"pass (Traffic Boost, $49 once, 7 days of Pro) or employee_m (AI Visibility Employee, done for you, $149/month)"New value: +"pass (Launch Kit, $79 once), tracker_m ($29/month) or tracker_y ($290/year) (Growth Tracker), employee_m ($149/month) or employee_y ($1490/year) (Growth Employee, done for you)"
    • changedInput schema / properties / plan / enum
      Previous value: -[
      -  "pass",
      -  "employee_m"
      -]New value: +[
      +  "pass",
      +  "tracker_m",
      +  "tracker_y",
      +  "employee_m",
      +  "employee_y"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / plan / description
      Previous value: -"pass (Fix Pack, $29 once, 7 days of Pro) or employee_m (AI Visibility Employee, done for you, $149/month)"New value: +"pass (Traffic Boost, $49 once, 7 days of Pro) or employee_m (AI Visibility Employee, done for you, $149/month)"
  3. Changed2 schema fields changed
    • changedInput schema / properties / plan / description
      Previous value: -"pass ($9 once, 7 days), pro_m ($19/month), pro_y ($190/year) or agency_m ($59/month)"New value: +"pass (Fix Pack, $29 once, 7 days of Pro) or employee_m (AI Visibility Employee, done for you, $149/month)"
    • changedInput schema / properties / plan / enum
      Previous value: -[
      -  "pass",
      -  "pro_m",
      -  "pro_y",
      -  "agency_m"
      -]New value: +[
      +  "pass",
      +  "employee_m"
      +]
  4. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true and openWorldHint=false; the description adds substantial behavior beyond that: payment happens externally on Dodo Payments, a license key arrives by email, that key should be passed as 'Authorization: Bearer <key>' for higher limits, and the checkoutOpen=false case yields a waitlist card rather than a purchase link. These are exactly the non-obvious traits an agent needs and cannot get from schema or annotations.

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 the purpose, then the post-purchase flow, then the edge case, with no filler. The relative clause around 'checkoutOpen' is dense but each sentence carries distinct information.

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?

With one enum parameter and no output schema, the description covers what the link is for, what the user does with it, and the not-on-sale branch. It could say slightly more about the return shape (a URL string) but nothing an agent needs to invoke it correctly 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?

Schema description coverage is 100% and the enum already spells out each plan's name, billing cadence, and price, so the description adds no per-plan meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 ('Get the Dodo Payments checkout link') plus its scope ('for one RankRoot plan, to hand to the user'), so an agent knows exactly what is produced. It does not explicitly contrast itself with the sibling get_pricing, which is the main thing keeping it from a 5.

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 states the operative context clearly: the link is meant to be handed to the user, and it handles the alternate branch where checkoutOpen is false (link is a pricing card for the waitlist). It stops short of naming alternatives such as get_pricing for comparing plans before checkout.

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