Skip to main content
Glama

xchain_build_lock

Destructive

[STATE] Build the unsigned EVM lockTranche tx to lock your leg's payout tranche after both legs fund. Pass the match payload from xchain_find_match/status; the operator's match-live signature inside it authorizes the lock — permissionless, you pay only gas. Returns {to, data, value_wei, chain, match_id} to sign and submit with your EVM wallet. Must land before settle (settle requires Locked). 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_lock"
  }
}

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

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

Goes well beyond the annotations by disclosing that the operator's match-live signature pre-authorizes the lock, that the call is permissionless and the caller pays only gas, and by spelling out the return payload since no output schema exists. The one gap is not stating reversibility/expiry of the lock or the refund escape hatch, which matters for a destructiveHint=true operation.

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?

One dense paragraph that front-loads the action, then the input, then the output, then the ordering constraint — no filler sentences. The leading "[STATE]" tag and some compressed jargon ("match-live signature") slightly reduce immediate readability.

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?

For a one-parameter builder with no output schema, it supplies everything an agent needs: the input source, the authorization model, the exact return fields, the gas-cost expectation, and the sequencing constraint relative to settle. Nothing material is left to guesswork.

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 parameter at 100% schema description coverage, so the schema already establishes it is the `match` payload from xchain_find_match / xchain_match_status. The description only adds that the operator's match-live signature inside that payload is what authorizes the lock — useful but marginal, consistent with the baseline.

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?

Names a specific verb and artifact: "Build the unsigned EVM lockTranche tx to lock your leg's payout tranche." The closing "EVM leg only" separates it from the cross-chain sibling xchain_build_lock_xmatch, so an agent can pick correctly without opening either schema.

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?

Gives explicit prerequisites and timing: "after both legs fund" and "Must land before settle (settle requires Locked)," plus the source of the input payload (xchain_find_match/status). It does not explicitly name which tool to use instead for the non-EVM/cross-chain leg, leaving that as an inference from "EVM leg only."

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