Skip to main content
Glama

game_reveal_guess

Destructive

[STATE] Reveal and resolve. Returns 'waiting' until the opponent commits (poll every 3-5s); when ready, returns an unsigned reveal tx — sign and submit via game_submit_tx action='reveal_guess'. The server supplies your persisted preimage and the matchup argument (shared cross-chain encoding). Correct guess recovers your ante plus the opponent's; wrong forfeits yours. Negative-sum after the treasury cut.

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": "game_reveal_guess"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations (destructive, non-idempotent, open-world), the description discloses the polling state machine ('waiting' until commit), the return payload shape (unsigned tx), the signing/submission requirement, and the economic outcome of a correct vs wrong guess including the treasury cut. This is exactly the behavioral context annotations 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?

Front-loaded with a bracketed state marker and a two-word action summary, then proceeds in order of agent need: poll behavior, return value, submission path, economics. Dense with jargon ('matchup argument (shared cross-chain encoding)') and slightly crammed into one block, but every sentence carries information.

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?

With no output schema and no parameters, the description does the heavy lifting by describing both return states and the follow-up submission step. Minor gaps remain around failure/expiry handling and what happens if the reveal window closes, but the core call path is fully covered.

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?

The tool takes zero parameters, so the baseline applies. The description adds meaningful context by explaining that the server supplies the persisted preimage and the matchup argument, which tells the agent why no inputs are needed.

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 ('Reveal and resolve') and clarifies that the tool only builds an unsigned reveal tx rather than submitting it. It does not explicitly distinguish itself from the sibling game_evm_reveal_guess or xchain_reveal_guess variants, so an agent must infer which chain-specific reveal to call.

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 concrete usage context: poll every 3-5s while the opponent has not committed, then sign and submit via game_submit_tx action='reveal_guess'. That is a clear when-to-use and a handoff to the correct sibling. It lacks an explicit when-not-to-use or a rule for choosing between this tool and the evm/xchain reveal 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