Skip to main content
Glama

game_evm_reveal_guess

Destructive

[STATE] Reveal your guess on-chain in a same-chain EVM match. Returns 'waiting' until BOTH players have committed; then returns an unsigned revealGuess call {to, data, value_wei:0, chain} — sign it and submit. The server recovers your persisted preimage and picks the correct rMatchup arg (the matchup preimage if you reveal first, the zero sentinel if second — read from chain via game-api). Requires a registered EVM wallet; pass your match's game_id. Reveal resolves the game per the payoff matrix.

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": {
      "game_id": "<game_id>"
    },
    "name": "game_evm_reveal_guess"
  }
}

Input Schema

NameRequiredDescriptionDefault
game_idYes0x game id of your same-chain EVM match (from the match payload).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the dual return modes ('waiting' versus an unsigned revealGuess call), the exact payload shape {to, data, value_wei, chain}, the requirement to sign and submit, and the server-side preimage recovery with rMatchup arg selection. This is exactly the state-machine detail the destructiveHint/idempotentHint flags cannot convey.

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 [STATE] tag and the return-shape explanation are front-loaded and the content is dense but earns its place. Minor cost: the parenthetical '(read from chain via game-api)' is implementation detail that does not help an agent decide or call correctly.

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?

For a stateful, sign-and-submit tool with no output schema and one parameter, the description covers return modes, prerequisites, and the preimage/arg-selection logic well. It omits failure behaviour (e.g., what happens if you call before committing, or if the reveal window has expired), which would matter for correct 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 coverage is 100%, so the game_id parameter is already fully documented in the schema, including the 0x format and match-payload origin. The description only restates 'pass your match's game_id' without adding format or validation meaning beyond that, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource — 'Reveal your guess on-chain' — and scopes it to 'a same-chain EVM match', which separates it from the xchain_* and generic game_reveal_guess siblings. An agent can identify the operation and the domain without opening the schema.

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?

Gives clear preconditions (registered EVM wallet, pass your match's game_id) and implies sequencing by explaining the tool returns 'waiting' until both players have committed. It stops short of explicitly naming an alternative tool for cross-chain reveals or stating when-not to use it, so it falls short of full routing guidance.

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