Skip to main content
Glama

game_evm_committed

Destructive

[STATE] Notify that you have committed your guess on-chain (commitGuess) in a same-chain EVM match. Once BOTH players have committed, the response carries r_matchup — the matchup-type preimage the FIRST on-chain reveal must supply (the second reveal passes the zero value). Before both commit, r_matchup is null (the anonymity barrier). Requires a registered EVM wallet; pass your match's game_id.

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

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

A3.8/5.0
Behavior3/5

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

Adds substantial behavior beyond the annotations: it explains the two-player commit threshold, that r_matchup is null before both commits (the anonymity barrier) and appears afterward, and that the first on-chain reveal must supply it while the second passes zero. That is genuinely useful state-machine context. It does not, however, explain why the tool is flagged destructive or what state it writes — the write/destructive profile rests entirely on the annotations, and the description reads like a passive notification, so it adds no color there.

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?

Front-loaded with the state transition and the payoff (r_matchup), and every sentence carries information about the protocol. The dense parenthetical clauses make it slightly telegraphic, but there is no filler.

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 only one parameter, the description covers what it must: the trigger event, the wallet prerequisite, and critically what the response carries and when (r_matchup null until both commit). An agent can call this correctly and interpret the return value from the description alone.

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% for the single game_id parameter, and the schema already notes it comes 'from the match payload'. The description only restates 'pass your match's game_id', adding no format, validation, or sourcing detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: notifying the server that a guess has been committed on-chain for a same-chain EVM match, with the commitGuess call named in parentheses. The 'same-chain EVM' qualifier implicitly separates it from the xchain_* family, though it never explicitly contrasts with the sibling game_evm_commit_guess that presumably submits the transaction itself.

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?

Makes the trigger condition clear (you have committed via commitGuess) and gives the prerequisite that a registered EVM wallet is required plus the instruction to pass the match's game_id. No explicit exclusions or named alternatives are given, so the agent must infer the ordering relative to game_evm_commit_guess rather than being told.

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