Skip to main content
Glama

Get RankRoot pricing

get_pricing
Read-only

List RankRoot plans (free scan, Launch Kit one-time, Growth Tracker monthly or yearly, done-for-you Growth Employee monthly or yearly) with prices, limits, checkout links and which plan fits which user. Agents with a USDC wallet can pay directly over x402: GET https://getrankroot.com/api/agent/check?url= ($0.50) or POST https://getrankroot.com/api/agent/employee {website} ($149, 30 days, key returned at once). Otherwise give the user the checkout link.

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_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Adds substantive context beyond the readOnlyHint/openWorldHint annotations: specific transaction prices ($0.50 for the check endpoint, $149 for the employee endpoint), that the key is returned immediately, and the 30-day duration. It does not describe the shape or volume of what this tool itself returns, so it stops short of full disclosure.

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?

Front-loads the plan enumeration, then moves to the agent payment path and the human fallback in two dense but purposeful sentences with no filler. The URL-and-price-heavy second half is compressed to the point of being slightly cryptic but every clause carries 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 zero parameters, no output schema, and annotations already marking it read-only and non-open-world, the description covers what an agent needs: what is returned (prices, limits, links, fit guidance) and how to complete a purchase. A brief note on response format or plan ordering would close the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is empty, so the baseline is 4. The description correctly adds no parameter discussion and instead spends its words on plan and payment semantics.

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?

Uses a specific verb plus resource ("List RankRoot plans") and enumerates the plan tiers and content returned (prices, limits, checkout links, plan-fit guidance). It does not name a sibling tool such as get_checkout_link, so an agent cannot distinguish it by explicit comparison, but the purpose itself is unambiguous.

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?

Provides an explicit conditional branch: agents holding a USDC wallet can pay directly over x402 at the named endpoints and prices, "Otherwise give the user the checkout link." That is clear routing based on agent capability. It stops short of stating when to prefer this tool over get_checkout_link or when pricing questions are out of scope.

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