Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Place an order

place_bet
Destructive

Places real buy or sell orders on prediction markets, spending or selling the user's balance and filling market or limit trades after the user confirms a simulated bet.

Instructions

Places a real order on a market: it spends or sells the user's actual balance and fills immediately against the book where it can. Only call it after the user has explicitly confirmed a get_bet_simulation with these same numbers. With a price it is a limit order (the unfilled part rests on the book unless time_in_force is ioc); without one it is a market order at the best available prices. Returns the created order, including its id, status and fills; use cancel_order to withdraw a resting order.

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": {
      "market": "<market>",
      "side": "<side>",
      "position": "<position>",
      "currency": "<currency>",
      "shares": "<shares>"
    },
    "name": "place_bet"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes`bid` buys shares; `ask` sells shares you already hold. To buy Yes use side bid with position long; to buy No use side bid with position short; to sell shares you hold use side ask with the position you hold.
priceNoLimit price per share, in whole cents between 0.01 and 0.99. A bid fills at this price or lower, an ask at this price or higher. Omit for a market order. Required for ioc and for shares "max".
marketYesMarket (outcome) id: the `id` of an entry in an event's `markets` list. This is not the event id.
sharesYesNumber of shares to buy or sell, at most 2 decimals and above 0.02. On side ask only, the string "max" sells every share you hold of this position that is not already reserved by an open sell order (requires `price`).
currencyYes`OOM` is play money. `USDC`, `USDT` and `USD` are real money and only work on events whose available_currencies include them.
positionYes`long` is the Yes side of the market (pays 1 if the outcome happens); `short` is the No side (pays 1 if it does not). Shares of each position trade in their own order book.
expired_atNoISO 8601 time (for example 2026-12-31T23:59:00Z) after which an unfilled resting order is cancelled automatically. Omit for no expiry.
time_in_forceNo`gtc` (default): the part that cannot fill now rests on the book until filled, cancelled or expired. `ioc`: fill what is possible right now at `price` or better and cancel the rest; requires `price`.
cancel_conflicting_ordersNoIf true, your own open orders that tie up the balance or shares this order needs are cancelled first. If false or omitted, such a conflict makes the order fail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, but the description adds the concrete consequence: real money is spent or shares sold, and fills happen immediately where possible. It also discloses the resting-order lifecycle (unfilled remainder rests unless time_in_force is ioc) and what the response contains (id, status, fills), which the annotations cannot convey.

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?

Purpose and the safety-critical confirmation gate are front-loaded, followed by order-type semantics and the response/alternative pointer. Every sentence carries information, though the middle sentences are dense and could be split for faster scanning.

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 destructive, non-idempotent 9-parameter mutation with no output schema, the description covers the gating requirement, order-type semantics, resting-order behavior, return contents, and the follow-up tool. Remaining details (cancel_conflicting_orders, expired_at, max shares) are fully documented in the schema.

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 100%, so the schema already documents each field and a baseline of 3 would be defensible. The description goes further by explaining the interaction between `price` and `time_in_force` (ioc cancels the remainder) and by framing the presence or absence of `price` as the limit/market decision, which is synthesis rather than restatement.

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?

"Places a real order on a market" gives a specific verb and resource, and the sentence immediately qualifies it as spending the user's actual balance with immediate fills against the book. This distinguishes it cleanly from get_bet_simulation (simulation) and cancel_order (withdrawal) without needing to open 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 Guidelines5/5

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

It states an explicit precondition: only call after the user has confirmed a get_bet_simulation with the same numbers. It also routes the agent to cancel_order for withdrawing a resting order and explains the price/no-price branch that selects limit vs market behavior.

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