Skip to main content
Glama

Graviton board

graviton_board
Read-onlyIdempotent

Free sample: https://apexfaucet.xyz/race/ ($0.001). Public Graviton standings. Betting is closed. Does not take a stake. Not advice. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses real cost ($0.001 per call), accepted payment rails (x402 USDC on Arc/Base/Solana, XNT on X1), and the two-phase terms-then-payment flow that a caller must follow. This is substantial context the readOnlyHint/idempotent hints do not convey. The only tension is that a purchase settles inside the call while readOnlyHint=true is declared; it concerns billing rather than data mutation, so it is not scored as a contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The price ($0.001) is stated twice, a free-sample URL leads the text ahead of the actual purpose, and "Not advice" is boilerplate. The payment-flow sentence is dense but useful; overall the definition is serviceable yet not front-loaded on what the tool does.

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

Completeness3/5

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

For a one-parameter read tool with no output schema, the description covers cost, auth flow, and the general nature of the content (standings). It does not describe what the standings contain, whether the result is paginated or time-scoped, or how it differs from graviton_state, leaving moderate gaps.

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?

Schema coverage is 100% and the single parameter is already documented, so the baseline would be 3. The description earns the extra point by explaining the sequencing semantics of `payment`: omit it first to receive terms, then supply a signed payload to complete the purchase in-call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Public Graviton standings" identifies the resource, but there is no verb and no differentiation from siblings such as graviton_state or graviton_how_to_play. The description opens with a promotional free-sample URL and pricing rather than the tool's purpose, so an agent must read past two clauses before learning what the tool returns.

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

Usage Guidelines3/5

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

"Betting is closed. Does not take a stake" sets useful expectations about what this tool is not, and the two-step payment protocol (call without `payment` for terms, sign, call again) is explicit invocation guidance. However, nothing says when to choose this over graviton_state or the other graviton_* siblings, so alternative selection is left to inference.

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