Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Simulate selling shares

get_partial_sell_amount
Read-only

Simulates the return from selling shares of a wager before you sell anything, returning amount, shares, and price for that position. Call it first to preview the proceeds, then confirm the sale.

Instructions

Simulates what selling shares of a wager would return, without selling anything: returns {amount, shares, price} for the user's wager. Production values the position from the current order-book bids; it can return an amount of 0 on the first call for a market while its book cache warms up, so call it again before believing a 0. Run this and show the result to the user before sell_bet. Pass the wager id, not a market id.

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

Input Schema

NameRequiredDescriptionDefault
idYesWager id, as returned by get_user_bets (field `id`). This is not a market id or an event id.
sharesNoNumber of shares to simulate selling; must not exceed the shares held in the wager. Omit to simulate selling the entire position.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint=true annotation, it discloses where values come from (current order-book bids), a real failure mode (returns 0 on first call while the book cache warms up, retry before believing it), and the interaction contract (show the result before selling). These are non-obvious traits an agent could not infer from annotations.

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?

Three tight sentences: what it returns, how values are sourced plus the warm-up caveat, then the workflow constraint. No filler, and the most important fact (simulation, nothing is sold) is front-loaded.

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?

With no output schema, the description supplies the return keys itself, and it covers the one behavioral trap (spurious 0) plus the read-only contract. Nothing an agent needs to call this correctly or interpret its result 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 coverage is 100% and the schema already documents both `id` (wager id, not market/event id) and `shares` (omit to sell entire position). The description's id guidance duplicates the schema field text, so it adds emphasis rather than new meaning; 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 ('Simulates what selling shares of a wager would return') and immediately scopes it as non-mutating ('without selling anything'), then names the exact return shape. An agent can distinguish it from sell_bet purely from this sentence.

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 explicit sequencing guidance ('Run this and show the result to the user before sell_bet') and an explicit negative constraint ('Pass the wager id, not a market id'). The alternative tool and the condition that selects it are both named.

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