Skip to main content
Glama

APEX 373 x402 & Card API-Key Agent Tools

Graviton state

graviton_state

Live Graviton Arena state for a wallet - your credit balance and the current round. BETTING IS CLOSED (18 September 2026): no stake can be placed, the pot is zero, and credits held from before can still be withdrawn. The arena itself is free to play.

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

Input Schema

NameRequiredDescriptionDefault
roundNo
walletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful state: betting closed as of 18 September 2026, zero pot, withdrawable pre-existing credits, free play. It omits whether the call is read-only, what happens if wallet is omitted (does it default to the caller?), and whether round defaults to the current round.

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 purpose and the most decision-relevant fact (betting closed) immediately after. No filler, though the closing 'free to play' sentence is marginal for a state-inspection tool.

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?

With no annotations, no output schema, and two undocumented optional parameters, the description covers purpose and arena status but leaves the input contract underspecified. An agent can understand why to call it but not confidently how to call it with round or wallet.

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

Parameters2/5

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

Schema coverage is 0% and both parameters are undocumented in the schema, so the description must compensate — but it never mentions 'round' or 'wallet' at all. The word 'for a wallet' hints at the wallet parameter but gives no format or default semantics, and round is entirely unaddressed.

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 resource (live Graviton Arena state for a wallet) and the contents it returns (credit balance, current round). It is distinguishishable from siblings like graviton_how_to_play and graviton_use_ability, though it never explicitly names those alternatives.

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?

It gives useful contextual guidance — betting is closed, stakes cannot be placed, credits can still be withdrawn, arena is free to play — which tells the agent this is a read/status check rather than an action. It does not explicitly state when to call it versus graviton_use_ability or graviton_how_to_play, leaving routing 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.