Skip to main content
Glama

Draft a perp order

draft_order
Read-only

Drafts a perpetual order as a link to Angler's trading screen with the order panel filled in (asset, long or short, size in USD, market or limit, leverage, take profit, stop loss, venue). It places nothing: the user opens the link, reviews the order and presses the button themselves. Use it to hand over a trade the user asked for.

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": {
      "symbol": "<symbol>",
      "side": "<side>",
      "size_usd": "<size_usd>"
    },
    "name": "draft_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYeslong buys, short sells.
venueNoOptional venue id (e.g. hyperliquid, lighter, aster); unset lets Angler route it.
symbolYesAsset ticker, e.g. BTC, ETH, NVDA.
leverageNoOptional; capped by the market's maximum on the site.
size_usdYesPosition size in USD (notional, not margin).
stop_lossNoOptional stop-loss price.
order_typeNoDefault market.
limit_priceNoRequired for a limit order.
take_profitNoOptional take-profit price.

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?

The annotations already declare readOnlyHint=true, and the description reinforces this with the critical detail that "It places nothing" and the user must review and press the button themselves — this is the key behavioral fact an agent needs to avoid treating it as trade execution. It does not cover link expiry, whether a URL is returned verbatim, or any auth requirements, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the non-execution guarantee front-loaded, followed by the selection guidance. No redundant or filler wording.

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 9-parameter drafting tool with full schema coverage and no output schema, the description covers what is produced (a pre-filled link) and the human-in-the-loop boundary. Minor gaps remain around the exact return payload and whether the link persists, but nothing essential to correct invocation is missing.

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%, so the schema already documents every parameter including enums and defaults. The description's parenthetical field list mirrors the schema rather than adding new semantics such as limit_price/order_type dependency rules, so 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 uses a specific verb and resource ("Drafts a perpetual order") and immediately clarifies the mechanism: a link to Angler's trading screen with the order panel pre-filled. It enumerates the pre-filled fields, so an agent can distinguish this from siblings like draft_bot or the read-only market data tools without inspecting the 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?

"Use it to hand over a trade the user asked for" gives a clear usage condition tied to user intent. It does not explicitly name alternatives or state when not to use it, but the context is unambiguous enough for correct selection.

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