Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

List my orders

list_orders
Read-only

Retrieve and filter your own Futuur orders by status, market, side, or currency; results default to open orders newest first, with paging to review filled or cancelled history.

Instructions

Lists the user's own orders, newest first by default, 20 per page. Without status it returns only open orders (including ones still processing); pass another status to see filled, cancelled or partially filled history. Each order has id, market, side, position, price, shares requested and unfilled, shares_filled, status, average_price and expiry. Use the id with cancel_order.

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": "list_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNoOnly buys (`bid`) or only sells (`ask`).
eventNoOnly orders on this event id.
limitNoOrders per page, 1 to 20. Default 20.
marketNoOnly orders on this market (outcome) id.
offsetNoOrders to skip, for paging. Default 0.
searchNoText to look for in the event or market title.
statusNoOrder status. Default `open`, which also includes orders still `processing` and only covers events that are still open. `partial_filled_cancelled` is an immediate-or-cancel order that filled in part and had the rest cancelled.
currencyNoOnly orders in this exact currency.
orderingNoSort order, default `-created` (newest first). A leading `-` means descending; `total` is the shares requested.
currency_modeNoOnly play-money (OOM) or only real-money orders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral context beyond that: the surprising default filter (open only, and only events still open), newest-first ordering, 20-per-page paging, and the exact fields returned per order. It stops short of describing pagination termination or total counts.

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?

Four tight sentences, front-loaded with scope and defaults, then the return shape, then the cross-tool pointer. Minor redundancy with the schema on the status default, but nothing is wasted.

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 10-parameter read tool with no output schema, the description supplies the missing return-value information (field list) and the default-filter behavior an agent needs to interpret results correctly. Nothing essential to a correct call is absent.

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 all ten parameters are already documented, including the status enum semantics and ordering prefix convention. The description only restates the status default and ordering default, adding little beyond the schema; 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?

States a specific verb and resource with scope ('the user's own orders'), plus default ordering and page size. The scope phrase distinguishes it from market-wide siblings like get_order_book, and the closing pointer to cancel_order anchors it in a workflow.

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?

Explains the critical default: without `status` only open orders (including processing) come back, and tells the agent to pass another status to reach filled/cancelled history. It also names the follow-up tool for the returned id. No explicit when-not guidance, but the default-behavior warning covers the main misuse risk.

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