Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Sell a bet

sell_bet
Destructive

Sells all or part of an open wager position, either immediately at the best bids or as a limit order, after a confirmed simulation. Requires the wager ID; omit shares to exit the whole position.

Instructions

Sells all or part of an open wager (position) for the user. It moves the user's balance and cannot be undone, so only run it after the user has confirmed a simulation for the same wager and shares (get_bet_simulation with side ask, or get_partial_sell_amount). Pass the wager id; omit shares to sell the whole position. On order-book events, which is every current market, the sale is placed as a sell order on the wager's market: without price it sells immediately at the best bids, with price it is a limit order that may rest on the book. The result then contains the created 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": {
      "id": "<id>"
    },
    "name": "sell_bet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWager id, as returned by get_user_bets (field `id`). This is not a market id or an event id.
priceNoOrder-book events only: minimum price per share to accept, in whole cents between 0.01 and 0.99. Omit to sell immediately at the best available bids.
sharesNoNumber of shares to sell. Omit to sell the entire position. Must not exceed the shares held; selling all of them is the same as omitting it.

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 flag destructive and non-idempotent, but the description adds the crucial consequence ('moves the user's balance and cannot be undone') plus market microstructure behavior: without price it hits the best bids, with price it may rest on the book as a limit order. That is real behavioral context 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?

Front-loaded with the action and its irreversibility, then prerequisites, then order-book mechanics. Dense and mostly waste-free, though the final sentence about the returned `order` is somewhat tacked on and could merge with the order-book sentence.

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?

No output schema exists, yet the description tells the agent the result contains the created `order`, and it covers side effects, preconditions, and limit-vs-market semantics for all three parameters. Nothing needed to invoke it safely is missing.

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 a 3 is the floor. The description still adds meaning by explaining the price/no-price branch as a market-vs-limit order decision and by reiterating the omit-shares shortcut, which clarifies intent rather than just repeating types.

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: 'Sells all or part of an open wager (position) for the user.' It clearly delimits the operation from place_bet and from the read-only siblings it names as prerequisites.

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?

Gives an explicit precondition ('only run it after the user has confirmed a simulation for the same wager and shares') and names the two tools that produce that confirmation (get_bet_simulation with side ask, or get_partial_sell_amount). The omit-shares case is also specified.

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