Skip to main content
Glama

xchain_gameplay_status

Read-onlyIdempotent

[READ] Your cross-chain 'what to sign next' view: the canonical step-2 checkpoint to co-sign once both players commit, the revealed r_matchup once the step-2 checkpoint is stored (so you can learn the matchup type and reveal), and the canonical terminal checkpoint once both reveal. Sign each returned checkpoint's digest with your session key and submit via xchain_sign_checkpoint.

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

Input Schema

NameRequiredDescriptionDefault
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/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description focuses on what the tool returns and under which state transitions each item appears. That adds real value: the agent learns the response is state-conditional and that the payload must be signed with a session key and submitted elsewhere. It does not describe behavior when no checkpoint is available yet, which is a minor gap.

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?

One dense but front-loaded sentence sequence: the [READ] tag and the core framing come first, then the three state-gated returns, then the action instruction. No filler, though the parenthetical clauses make it a heavy run-on that could be split for scanability.

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

Completeness3/5

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

With no output schema, the description correctly spends its words enumerating the three possible return artifacts and their preconditions, which is the essential information. However it omits the empty-state case (nothing to sign yet) and says nothing about how the caller should proceed if a returned checkpoint is already signed, leaving a workflow gap for a stateful poller.

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 description coverage is 100%, including the poll_handle semantics and its rollout-optional status, so the schema carries this burden. The description never mentions poll_handle and adds no meaning beyond it, which is the baseline case for a single fully documented parameter.

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 states a specific read operation with a concrete framing ("cross-chain 'what to sign next' view") and then enumerates the exact artifacts it returns: the step-2 co-sign checkpoint, the revealed r_matchup, and the terminal checkpoint. It is distinguishable from sibling xchain_sign_checkpoint by explicitly handing off the signing action there, and from match-status tools by its focus on next-to-sign artifacts.

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 clear stage-based conditions for reading (after both players commit, after the step-2 checkpoint is stored, after both reveal) and states the follow-up action to take with each result. It does not explicitly state when not to use it versus xchain_match_status, so it stops short of full routing guidance.

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