Skip to main content
Glama

xchain_build_create_xmatch

Destructive

[SPEND: the configured stake] Build the matchmaker-cosigned Solana create_xmatch tx that funds your leg of a matched cross-chain game. Returns {unsigned_tx, blockhash, matchmaker_signature, match_id}: add your wallet signature and broadcast via game_submit_tx action='create_xmatch'. The matchmaker only cosigns txs the backend built for your real pending match. Solana leg only.

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

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

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

Annotations already flag this as destructive, non-idempotent, open-world and not read-only, but the description adds real context: it spends the configured stake, it is cosigned only for a genuine pending match, it returns a specific set of fields, and it requires a wallet signature plus a separate broadcast call. The only gap is failure behavior when no pending match exists.

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?

Three sentences, each carrying distinct information, with the cost tag and core purpose front-loaded. It is dense and slightly packed into single long lines, but no sentence is redundant.

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?

Although there is no output schema, the description enumerates the returned fields, the stake cost, the cosigning constraint, the required follow-up broadcast, and the chain scope. An agent has everything needed to invoke it and interpret the result 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?

The single parameter, poll_handle, is already fully documented in the schema (100% coverage), including its unguessable-secret rationale and optional status. The description adds nothing about it, so the baseline of 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?

The description names a specific verb and resource ('Build the matchmaker-cosigned Solana create_xmatch tx') and immediately states the business effect: it funds your leg of a matched cross-chain game. The closing 'Solana leg only' scopes it apart from the EVM-side and match-creation siblings.

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 an explicit next step ('add your wallet signature and broadcast via game_submit_tx action="create_xmatch"') and states a precondition: the matchmaker only cosigns txs for your real pending match. It does not explicitly contrast with xchain_build_create_match or say when-not to call it, so it stops short of full when/when-not 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