Skip to main content
Glama

xchain_match_status

Read-onlyIdempotent

[READ] Poll for your cross-chain match. Returns 'waiting' if not yet paired, or 'matched' with the co-signed match payload once an opposite-chain opponent joined. Call after xchain_find_match returned 'waiting'. Pass the poll_handle it returned so you poll by an unguessable secret rather than your public wallet. Requires a registered wallet.

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

Input Schema

NameRequiredDescriptionDefault
poll_handleNoThe `poll_handle` returned by xchain_find_match. Pass it so you poll by an unguessable secret rather than your public wallet. Optional during rollout: omitting it falls back to a (deprecated) wallet lookup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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), and the description adds genuinely new context: the two-state return contract, the auth prerequisite ("Requires a registered wallet"), and the security rationale for polling by secret. It does not state polling cadence, timeout/expiry behavior, or error cases, which matters for a poll tool.

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?

Four sentences, each earning its place, with the [READ] tag and purpose front-loaded followed by return values, invocation trigger, parameter guidance, and prerequisite in a logical order. 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?

For a single-optional-parameter polling tool with no output schema, the description supplies the return states inline, the calling precondition, and the auth requirement. An agent has everything needed to select and invoke it correctly.

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% and the schema's poll_handle field already explains the unguessable-secret rationale and the deprecated wallet fallback. The description restates the same point rather than adding new semantics, so baseline 3 applies.

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?

States a specific verb and resource ("Poll for your cross-chain match") and enumerates the two possible outcomes ('waiting' vs 'matched' with co-signed payload). It is clearly distinguishable from sibling xchain_find_match, which it explicitly references.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition: "Call after xchain_find_match returned 'waiting'." That names the alternative tool and the exact state that selects this one, leaving nothing to inference.

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