Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Get wager details

get_wager_details
Read-only

Inspect a single wager by ID to review status, position, shares, cost basis, ROI, payout, sell value, and action history. Use it to verify a position or confirm sale results.

Instructions

Returns one wager by its wager id: status, long or short position, shares held, cost basis, ROI, what it pays if it wins (amount_on_win), what it would sell for now (amount_on_sell), the market and event it belongs to, and the actions history of purchases, sales and resolution. Use it to inspect a position or to check the result after a sale. event.order_book_enabled tells you how the position can be sold; see sell_bet. Get wager ids from get_user_bets.

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_wager_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWager id, as returned by get_user_bets (field `id`). This is not a market id or an event id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds substantial value by enumerating the returned fields, including the actions history of purchases, sales and resolution, and the presence of a nested event object. It also discloses that event.order_book_enabled governs sellability, a non-obvious behavioral coupling. It does not say what happens for an unknown or unauthorized wager id, which keeps it short of 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.

Conciseness4/5

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

Front-loaded with the core statement, then the return payload, then the routing hints; there is no filler. The field enumeration is dense but earns its place because no output schema exists, though the paragraph would scan better if the routing hints were separated from the return-field list.

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?

There is no output schema, and the description compensates by naming the return payload including nested market, event and actions data. Combined with the id-provenance hint and the sell_bet pointer, an agent has everything needed to call it correctly and interpret the result.

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 single parameter's schema entry already states it is a wager id from get_user_bets and explicitly not a market or event id. The description restates the same provenance without adding format, range, or failure semantics, so the schema is doing the work and 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?

"Returns one wager by its wager id" gives a specific verb (returns) and a specific resource (a single wager), then enumerates exactly what that record contains. It is clearly distinguished from sibling get_user_bets (which supplies the ids) and from market/event detail tools by the explicit note that the id is neither a market id nor an event id.

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?

Names two concrete use cases ("inspect a position" and "check the result after a sale") and routes the agent to the correct upstream tool for ids ("Get wager ids from get_user_bets") and the correct downstream tool for liquidation ("see sell_bet"). The conditional pointer to event.order_book_enabled explains how to decide whether the position can be sold at all, which is exactly the kind of when-to guidance an agent needs.

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