get_checkout_linkGet the Polar checkout link for one RankRoot plan, to hand to the user. The user pays on Polar and receives a license key by email; pass it as 'Authorization: Bearer ' for higher API/MCP limits. If checkoutOpen is false, the link is an application form the user fills in instead.
| Name | Required | Description | Default |
|---|---|---|---|
| plan | Yes | pass (Traffic Boost, $49 once, 7 days of Pro) or employee_m (AI Visibility Employee, done for you, $149/month) |
Changes observed during successful MCP inspections.
Input schema / properties / plan / descriptionPrevious 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)"Input schema / properties / plan / descriptionPrevious 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)"Input schema / properties / plan / enumPrevious value: -[
- "pass",
- "pro_m",
- "pro_y",
- "agency_m"
-]New value: +[
+ "pass",
+ "employee_m"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With annotations already declaring readOnlyHint=true and openWorldHint=false, the description adds substantial context beyond the schema: the payment happens on Polar, the user receives a license key by email, that key can be passed as a Bearer token for higher limits, and checkoutOpen=false changes the link into an application form. These are useful downstream-behavior details not captured by annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences and front-loads the main action before adding useful downstream context. It is efficiently sized, though the Bearer-token detail is somewhat tangential to obtaining the link.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, but the description explains what the returned link is used for and how its meaning changes when checkoutOpen is false. That is enough for an agent to call and interpret the tool correctly, though it stops short of describing the exact return shape.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the enum values already document what 'pass' and 'employee_m' mean in detail. The description only says the tool is for 'one RankRoot plan' and adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb and resource: 'Get the Polar checkout link for one RankRoot plan,' which is clear and unambiguous. It does not differentiate from related sibling tools such as get_pricing, but no direct duplicate checkout-link sibling exists, so 4 is appropriate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'to hand to the user' implies the intended use case, but there is no explicit guidance on when to choose this tool over get_pricing or other alternatives. The conditional note about checkoutOpen adds behavioral context rather than usage rules.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.