Skip to main content
Glama

game_evm_commit_guess

Destructive

[STATE] Commit your guess on-chain in a same-chain EVM match: 'same' (opponent is your type) or 'different'. Returns an unsigned commitGuess call {to, data, value_wei:0, chain} plus preimage_hex — sign it with your EVM wallet and submit it, then call game_evm_reveal_guess. The server generates and persists the commitment preimage (mirrors the Solana game_commit_guess). Requires a registered EVM wallet; pass your match's game_id. No funds move (stake was locked at createGame/joinGame).

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

Input Schema

NameRequiredDescriptionDefault
guessYesYour guess: "same" or "different".
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.4/5.0
Behavior5/5

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

Beyond annotations it discloses the concrete return shape ({to, data, value_wei:0, chain} plus preimage_hex), that the server generates and persists the preimage, that the call is unsigned and must be signed and submitted by the caller, and that no funds move because stake was locked earlier. This is exactly the kind of operational context the destructiveHint=true / openWorldHint=true annotations do not explain on their own.

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 paragraph is front-loaded with the action and the state tag, and every clause (return shape, preimage persistence, wallet prerequisite, no-funds-movement) carries information. The inline object notation and parenthetical Solana reference add minor density but no real waste.

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

Completeness5/5

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

With no output schema and a mutation-style tool, the description still supplies the return payload shape, the follow-up tool, the prerequisite wallet state, and the funds semantics. An agent has everything needed to invoke it and handle the result correctly.

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% and both parameters already document their meaning, including the 'same'/'different' options. The description repeats the guess values but adds no format, validation, or edge-case detail beyond what the schema provides, so this sits at the baseline.

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?

The description opens with a specific verb and scope: 'Commit your guess on-chain in a same-chain EVM match.' It defines the two allowed guess values and explicitly positions itself as the EVM counterpart to the Solana game_commit_guess, so an agent can distinguish it from game_commit_guess and xchain_commit_guess without opening any 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?

It gives the correct sequence: sign the returned unsigned call with your EVM wallet, submit it, then call game_evm_reveal_guess, and states the prerequisite of a registered EVM wallet plus passing the match's game_id. It does not explicitly exclude the Solana or cross-chain variants, but the 'same-chain EVM match' framing and the Solana mirror note make the intended context clear.

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