Open Claw x402 Tools

live_grade

Read-only

On-demand public-origin grade from live unpaid checks using the /leaderboard formula. Price $0.04 (40000 atomic USDC on Base). Pays via x402.

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": {
      "origin": "<origin>"
    },
    "name": "live_grade"
  }
}

Input Schema

Name	Required	Description
`url`	No	Public door URL used to derive origin. Alias of origin.
`host`	No	Public hostname used to derive https origin. Alias of origin.
`origin`	Yes	Public https origin to grade from live unpaid checks. Required unless url or host is set. Localhost and tunnels are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

C2.7/5.0

Behavior1/5

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

The annotations declare readOnlyHint=true, but the description says 'Price $0.04 ... Pays via x402,' which implies a payment/financial side effect during invocation. That directly conflicts with a read-only annotation; the openWorldHint=true part is consistent with live external checks, but the read-only contradiction is serious.

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?

The description is compact and front-loads the core purpose before adding pricing/payment details. Every sentence carries relevant information, though the pricing and x402 sentence is only partially integrated with the usage guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, open-world grading tool with no output schema, the description is thin: it does not explain what the grade result contains, how payment via x402 is actually handled, or what errors/limits to expect. It gives the price and formula source, but not enough behavioral context for confident invocation.

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%, so the input schema already documents url, host, and origin fully. The description adds no parameter-level meaning beyond the already-complete schema, making the baseline 3 appropriate.

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 states a specific verb-like action and resource: an on-demand public-origin grade derived from live unpaid checks using the /leaderboard formula. It is distinguishable from most siblings, though it does not explicitly contrast with writing_grade or other grading-adjacent tools.

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

Usage Guidelines2/5

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

It says the grade is 'on-demand' and based on live unpaid checks, but gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance. The agent must infer the usage context from the purpose alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Open Claw x402 Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?