Skip to main content
Glama

xchain_build_refund_xmatch

Destructive

[STATE] Build the unsigned permissionless Solana refund tx for your cross-chain leg. Pass the match payload + kind='timeout' (claim window elapsed) or 'nocert' (funded but never locked/cosigned). Sign and broadcast via game_submit_tx. Solana leg only; EVM players use xchain_build_refund.

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": {
      "match": "<match>"
    },
    "name": "xchain_build_refund_xmatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo"timeout" (default) or "nocert".
matchYesThe `match` payload object from xchain_find_match / xchain_match_status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds crucial context those annotations cannot convey: the output is unsigned (this tool does not submit anything) and permissionless, and the actual broadcast happens elsewhere via game_submit_tx. It does not cover failure modes or what exactly comes back in the transaction payload, keeping it below a 5.

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?

Three short sentences, front-loaded with the core action and the conditional modes, then the next step, then the sibling exclusion. The [STATE] tag and parenthetical glosses are compact and every clause 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?

For a two-parameter builder tool with no output schema, it covers purpose, mode selection, the follow-up action, and the cross-chain routing boundary. It stops short of describing what the returned unsigned transaction contains or how errors surface, which is a minor gap for a build-only step.

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, but the description genuinely enriches the semantics of the `kind` value by explaining what game state each option corresponds to (claim window elapsed vs. funded but never locked/cosigned), which the schema's one-line enum gloss does not. It also confirms `match` comes from find/status lookups, though that is already in the schema.

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 ('Build the unsigned permissionless Solana refund tx') and immediately scopes it to a cross-chain leg. It also explicitly differentiates itself from the sibling xchain_build_refund by stating 'Solana leg only; EVM players use xchain_build_refund.'

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 the exact trigger conditions for each mode: kind='timeout' when the claim window has elapsed, and 'nocert' when funds were sent but never locked/cosigned. It names the alternative tool for the EVM leg and states the required follow-up step ('Sign and broadcast via game_submit_tx'), 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