Skip to main content
Glama
Sign In

OwlGate

by xyz.owlgate
OverviewDiscussionsAdmin

Publish a Signed X Layer Order

xl_post_order

Publish an order you built with xl_build_order and signed (EIP-712 typed data, free, no gas) to the OwlGate book on X Layer: pass the order object from the post step and your signature. OwlGate checks the signature, funds and approval before it goes live. Returns the order hash (use it with xl_cancel).

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": {
      "order": "<order>",
      "signature": "<signature>"
    },
    "name": "xl_post_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYesbody.order from the xl_build_order post step
signatureYesSignature from the sign step (0x…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations only cover safety hints (not read-only, open world, not destructive), while the description adds real behavior: signing is free with no gas, OwlGate validates signature, funds and approval before the order goes live, and the call returns an order hash. It still doesn't say whether a published order can be re-published or what a rejection looks like, which keeps it from a 5.

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?

Everything is packed into a single front-loaded sentence with the action, the prerequisite chain, the validation behavior and the return value in order of relevance. The parenthetical about EIP-712 and no gas is dense but earns its place; the sentence is long 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?

For a two-parameter mutation with no output schema, the definition covers the prerequisites, what gets validated server-side, and the shape of the return value (order hash) plus its follow-up use. Only idempotency and failure behavior are left unstated, which is a minor gap at this complexity.

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 description coverage is 100%, and the schema already explains that 'order' is body.order from the xl_build_order post step and 'signature' is the 0x… signature. The description largely restates that provenance, adding little beyond what the structured fields provide, so the baseline 3 applies.

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 verb and resource: publish a signed order to the OwlGate book on X Layer. It explicitly ties the input to xl_build_order and the output to xl_cancel, so an agent can separate this tool from its siblings 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the sequence for use: build with xl_build_order, sign, then publish with the order object and signature, and keep the returned hash for xl_cancel. It doesn't say when NOT to use it or what happens if the order is already published, but the prerequisite context is strong enough to guide correct selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OwlGate toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources