Skip to main content
Glama

game_commit_guess

Destructive

[STATE] Commit your guess on-chain: 'same' (opponent is your type) or 'different'. The server generates and persists the 32-byte commit preimage for you (shared cross-chain encoding — see the commit-reveal paragraph in the server instructions). Returns an unsigned commit tx — sign and submit via game_submit_tx, then poll game_reveal_guess. No funds move here (stake locked at game_find_match).

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>"
    },
    "name": "game_commit_guess"
  }
}

Input Schema

NameRequiredDescriptionDefault
guessYesYour guess: "same" or "different".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description usefully clarifies the scope of that destructiveness by noting no funds move here because the stake was locked at game_find_match. It also discloses a non-obvious side effect — the server generates and persists the 32-byte commit preimage — and that the return value is an unsigned tx. It does not address idempotency or what happens on a repeat commit, despite idempotentHint=false.

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?

It is front-loaded with a state marker and the core action, then the side effects, then the follow-up workflow. Nearly every clause carries information, though the cross-reference to the server instructions' commit-reveal paragraph is a slightly costly detour for a one-parameter tool.

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?

For a one-parameter commit step, the description covers the action, the value semantics, the server-side preimage side effect, the unsigned-tx return, the required signing step, and the subsequent poll. With no output schema needed and annotations carrying the safety profile, nothing essential is missing.

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 above baseline by explaining the semantic meaning of the value 'same' (the opponent matches your type) and noting the shared cross-chain encoding, which the schema does not convey.

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 states a specific verb and resource ('Commit your guess on-chain') plus the two allowed values and the meaning of 'same' ('opponent is your type'). It is clear about what the tool does, but it does not distinguish this tool from the near-identically named siblings game_evm_commit_guess and xchain_commit_guess, which an agent could easily confuse it with.

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 explicit workflow context: this produces an unsigned tx, which must be signed and submitted via game_submit_tx, after which the agent should poll game_reveal_guess. That names concrete next-step alternatives and the ordering. It stops short of stating when NOT to use this tool (e.g. versus the EVM/xchain commit variants).

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