Skip to main content
Glama

xchain_reveal_guess

Destructive

[STATE] Reveal your cross-chain guess after both committed and you co-signed the step-2 checkpoint. Pass preimage = 0x + your 32-byte R (the value whose SHA-256 you committed). Returns {both_revealed}; then xchain_gameplay_status for the terminal checkpoint and xchain_build_settle.

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": {
      "preimage": "<preimage>"
    },
    "name": "xchain_reveal_guess"
  }
}

Input Schema

NameRequiredDescriptionDefault
preimageYes`0x` 32-byte guess preimage that opens your commit.
poll_handleNoThe poll_handle returned by xchain_find_match. Pass it so the server acts by an unguessable secret, not your public wallet. Optional during rollout.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the required value relationship ('0x + your 32-byte R' whose SHA-256 was committed) and the return shape ({both_revealed}). The annotations already flag the operation as state-changing, destructive, and non-idempotent, so the description's addition of sequencing and return context is meaningful without needing to restate safety semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: state condition first, then the required parameter derivation, then the return value and follow-up tools. Every sentence carries useful information with no redundant restatement.

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 stateful cross-chain reveal step with no output schema, the description supplies the precondition, the exact parameter construction, the immediate return value, and the next tools to call. That is sufficient for an agent to invoke it correctly in sequence.

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%, so the baseline is 3. The description still adds meaning by explaining that `preimage` must be the exact 0x-prefixed 32-byte R whose SHA-256 was previously committed, which clarifies the commit-reveal relationship beyond the schema's shorter wording.

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 opens with a specific verb and resource ('Reveal your cross-chain guess') and adds a clear state precondition ('after both committed and you co-signed the step-2 checkpoint'). It does not explicitly distinguish itself from siblings such as game_reveal_guess, but the cross-chain framing makes its purpose clear.

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 states exactly when to call it (after both commitments and the step-2 checkpoint co-sign) and names follow-up tools (xchain_gameplay_status, xchain_build_settle). It does not discuss when not to use it or contrast it with non-cross-chain reveal siblings, so it falls short of the explicit alternatives expected at 5.

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