Skip to main content
Glama

xchain_build_lock_xmatch

Destructive

[STATE] Build the unsigned permissionless Solana lock_xtranche tx (lock your Solana leg's tranche after both legs fund). The operator's stored match-live signature authorizes it; you are the cranker and pay only the fee. Sign and broadcast via game_submit_tx action='lock_xtranche'. Must land before settle. Solana leg only; EVM players use xchain_build_lock.

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

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true; the description adds genuinely new context: the tx is unsigned, the operator's stored match-live signature authorizes it, and the caller is a cranker paying only the fee. It does not explain why the operation is flagged destructive or what happens if the tx fails to land before settle, so it stops short of full disclosure.

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 state tag and the core action, then sequencing, then the submission path, then the scope exclusion — a logical order with no filler. It is dense with protocol jargon ('cranker', 'match-live signature', 'tranche') that assumes domain fluency, which slightly reduces accessibility but not efficiency.

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 explains what is produced (an unsigned tx) and how to submit it, plus the timing constraint that governs success. The only gap is failure behavior and the role of the optional poll_handle, which is minor for a single-optional-param builder tool.

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?

There is a single optional parameter (poll_handle) with 100% schema description coverage, so the schema already carries its meaning. The description never mentions poll_handle or the unguessable-secret rationale, adding nothing beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 lock_xtranche tx', and immediately scopes it to the Solana leg while naming the sibling for the EVM case ('EVM players use xchain_build_lock'). An agent can distinguish this from xchain_build_lock and the other xchain_build_* tools without opening any schema.

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 preconditions ('after both legs fund'), a sequencing constraint ('Must land before settle'), the follow-up action ('Sign and broadcast via game_submit_tx action=\'lock_xtranche\''), and an exclusion routing EVM players elsewhere. When-to-use, when-not-to-use, and the alternative are all present.

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