Skip to main content
Glama

Build an X Layer Voucher Order (unsigned)

xl_build_order
Read-only

Unsigned steps to place an order on the X Layer voucher market (Seaport): kind list (sell one voucher you hold, price in OKB), offer (bid on one voucher, paid in WOKB) or coll (bid on any voucher). The seller pays a 0.75% OwlGate fee on fill. Steps: approve/wrap if needed (send), sign typed data (free), then publish with xl_post_order (pass body.order and the signature). The wallet signs itself; OwlGate never holds funds.

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": {
      "kind": "<kind>",
      "from": "<from>",
      "price": "<price>"
    },
    "name": "xl_build_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
vNoVoucher id (not needed for coll)
daysNoOrder lifetime in days (default 1)
fromYesWallet address (0x…)
kindYes
priceYesPrice in OKB, 0.01 to 500

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the 0.75% OwlGate fee on seller fills, which step costs gas versus which is free, and the custody model ('OwlGate never holds funds'). The readOnlyHint=true is consistent with a tool that only assembles unsigned steps and never broadcasts, and the description makes that separation clear rather than contradicting it. Missing: what the returned steps structure contains.

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 resource and the three kinds, then the step sequence. Dense but every clause carries information an agent needs (kinds, fee, currency, next tool). Slightly overloaded as a single block rather than separated lines, but 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 does most of the work: it explains that the output is unsigned steps feeding into xl_post_order. What it omits is the shape of those steps and the signing payload, which the agent must discover from the response. Adequate for a five-parameter builder tool with annotations present.

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 80%, and the description adds genuinely new meaning: price is denominated in OKB for list but in WOKB for offer, a currency distinction the schema flattens into 'Price in OKB'. It also reinforces that the voucher id is irrelevant for coll. It adds nothing on 'days' or on 'from' 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?

The description names a specific resource (X Layer voucher order via Seaport) and a specific action (build unsigned steps), then enumerates the three order kinds with one-line definitions (list = sell a held voucher priced in OKB, offer = bid paid in WOKB, coll = bid on any voucher). It also distinguishes itself from the sibling that finishes the job, xl_post_order.

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?

The usage sequence is spelled out: approve/wrap if needed (send), sign typed data (free), then publish with xl_post_order passing body.order plus the signature. That routes the agent between this tool and its sibling explicitly. It does not say when to pick xl_fill or buy instead of building an order, so it stops short of full alternative coverage.

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