Skip to main content
Glama

xchain_find_match

Destructive

[STATE] Join the cross-chain Coordination Game queue (Solana <-> EVM), live on Mainnet (Solana <-> Base / Ethereum) and Testnet (Solana Devnet <-> Base Sepolia). Prefer Base (eip155:8453) over Ethereum L1 (eip155:1) for ~$5 stakes, as L1 gas across createMatch, lockTranche, settle, and withdraw can exceed the stake. Generate a per-match secp256k1 session key locally and pass its 0x address — the server never sees the private key. Requires register_wallet (Solana base58 or EVM 0x). Returns 'waiting' (poll xchain_match_status until matched with an opponent) or 'matched' with the co-signed payload.

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": {
      "session_key": "<session_key>"
    },
    "name": "xchain_find_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_keyYes0x eth address of your per-match secp256k1 session key. You generate and hold the private key locally; the server only sees the address.
tournament_idNoOptional tournament ID. Omit to automatically join the active tournament for your wallet's network (3 on mainnet, 1003 on testnet).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tournament_id / description
      Previous value: -"Tournament ID to join. Defaults to 1."New value: +"Optional tournament ID. Omit to automatically join the active tournament\nfor your wallet's network (3 on mainnet, 1003 on testnet)."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations it discloses the key-handling model (session key generated locally, server never sees the private key), the prerequisite registration, the two possible return states, and real cost behavior. What it does not address is the destructiveHint=true commitment semantics — whether joining locks funds or whether the queue entry can be abandoned — which is the main behavioral question an agent would still have.

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 the action and the network scope, and each subsequent sentence carries distinct value (gas advice, key model, prerequisite, return states). It is dense — packed with chain IDs and function names — but not padded.

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?

With no output schema, the description correctly compensates by describing the two return shapes ('waiting' vs 'matched' with co-signed payload) and the polling follow-up. The remaining gap is the funding/commitment side of joining the queue, which matters given destructiveHint=true.

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 coverage is 100%, so both parameters are already fully documented, including the local-key rationale for session_key that the description largely restates. The optional tournament_id and its auto-join behavior are not mentioned in the description at all, so it adds little meaning beyond 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?

Opens with a specific verb+resource ('Join the cross-chain Coordination Game queue') and scopes it to Solana<->EVM on named mainnet and testnet networks. It also implicitly separates itself from xchain_match_status by telling the agent to poll that sibling after joining.

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 when-to-use guidance: prefer Base (eip155:8453) over Ethereum L1 for ~$5 stakes because L1 gas across createMatch/lockTranche/settle/withdraw can exceed the stake. It also names the register_wallet prerequisite and the follow-up path (poll xchain_match_status until matched).

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