Skip to main content
Glama

xchain_build_settle

[STATE] Fetch the operator-cosigned outcome of your finished cross-chain match, relay session-key settlement signatures, and assemble unsigned settle transactions. Call once to get outcome_digest, then re-call with live_signature and outcome_signature (plus match_payload on EVM) to record co-signatures on the relay. Once ready, returns 3-party live_sigs and oc_sigs plus solana_settle_tx (broadcast via game_submit_tx action='settle_xmatch') or evm_settle_call (sign and submit from your EVM wallet). If an opponent goes offline without co-signing terminal settlement, on-chain openClaim / refundTimeout paths protect staked funds; equivocated matches are rejected.

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

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.
match_payloadNoOptional `match` payload from `xchain_find_match` / `xchain_match_status`. Pass on the EVM leg so the server can also return `evm_settle_call`.
live_signatureNoOptional 0x 65-byte session-key signature over `match_live_digest` for the settle-sig relay.
outcome_signatureNoOptional 0x 65-byte session-key signature over `outcome_digest` for the settle-sig relay.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / live_signature
      Added value: +{
      +  "default": null,
      +  "description": "Optional 0x 65-byte session-key signature over `match_live_digest` for\nthe settle-sig relay.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / match_payload
      Added value: +{
      +  "default": null,
      +  "description": "Optional `match` payload from `xchain_find_match` / `xchain_match_status`.\nPass on the EVM leg so the server can also return `evm_settle_call`."
      +}
    • addedInput schema / properties / outcome_signature
      Added value: +{
      +  "default": null,
      +  "description": "Optional 0x 65-byte session-key signature over `outcome_digest` for the\nsettle-sig relay.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare non-readOnly, openWorld, non-idempotent, non-destructive; the description adds the two-phase call behavior, that co-signatures are recorded on the relay, the exact shape of the return (3-party live_sigs and oc_sigs, solana_settle_tx or evm_settle_call), and the failure semantics (offline opponent, equivocated matches rejected). Nothing in the text conflicts with the annotations, since recording signatures on the relay justifies readOnlyHint=false.

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 state tag and the core action, and every clause carries distinct information (flow, return values, routing, fallback). It is a dense single paragraph, though, and the mid-sentence parentheticals make it heavier to scan than it needs to be.

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?

No output schema exists, yet the description still enumerates the returned fields and what to do with each, and it covers the adverse paths. For a multi-step, cross-chain settlement tool this is enough for an agent to call it correctly.

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 already 100%, so the baseline is 3; the description adds real sequencing meaning by specifying which parameters belong to the second call (live_signature, outcome_signature) and that match_payload is EVM-leg-only. It does not add much about poll_handle beyond what the schema says.

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 specific verbs and resources: 'fetch the operator-cosigned outcome', 'relay session-key settlement signatures', 'assemble unsigned settle transactions'. It also distinguishes itself from game_submit_tx by naming that tool as the broadcast step for solana_settle_tx, so the agent knows this tool builds rather than submits.

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 explicit sequencing: 'Call once to get outcome_digest, then re-call with live_signature and outcome_signature (plus match_payload on EVM)'. It also routes the downstream action (broadcast solana_settle_tx via game_submit_tx action='settle_xmatch', or sign/submit evm_settle_call from the EVM wallet) and names the fallback (openClaim / refundTimeout) when an opponent goes offline.

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