Skip to main content
Glama

xchain_build_create_match

Destructive

[SPEND] Build the unsigned EVM createMatch call funding your leg of a matched cross-chain game. Pass the match payload from xchain_find_match/status. Returns {to, data, value_wei, chain, fund_deadline, match_deadline} — sign with your EVM wallet (fill gas/nonce locally); value_wei is your stake in native coin. EVM leg only.

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

Input Schema

NameRequiredDescriptionDefault
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
Behavior5/5

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

Goes well beyond the annotations by disclosing that the output is unsigned, enumerating the returned fields, and stating the caller must sign and fill gas/nonce locally. It also clarifies that value_wei is the native-coin stake, which is essential context for a destructive spend operation.

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 tight sentences, front-loaded with the [SPEND] tag and the action, then input source, then return shape and signing responsibility. No filler.

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 compensates by listing the return fields and the signing obligation. Minor gap: it does not explain what fund_deadline/match_deadline mean or what happens if they lapse, which matters for a time-sensitive spend.

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 adds real value by identifying the provenance of the `match` payload (xchain_find_match/status), which the schema alone does not convey.

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 EVM createMatch call") plus the scope ("funding your leg of a matched cross-chain game") and explicitly limits it to the EVM leg, which separates it from the xmatch sibling.

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?

Tells the agent where the required input comes from ("Pass the `match` payload from xchain_find_match/status") and scopes usage with "EVM leg only", implicitly routing non-EVM cases elsewhere. It stops short of naming the alternative tool or stating exclusions explicitly.

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