Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

List my bets

get_user_bets
Read-only

Lists wagers with pagination, newest first, defaulting to the authenticated user's own positions and filtering by open or settled status, event, following, or currency mode.

Instructions

Lists wagers (positions) with pagination, newest first; by default the authenticated user's own. Each wager has its wager id, status (purchased = open, sold, won, lost, cancelled, disabled), position (long or short), shares, currency, the cost basis, the current sale value (amount_on_sell), plus the market (id, title) and event (id, title, order_book_enabled) it belongs to. Use active for open positions or past_bets for settled ones; pass a wager id to get_wager_details for the purchase and sale history. At most 20 wagers per page.

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

Input Schema

NameRequiredDescriptionDefault
userNoAnother user's id, to read their public play-money wagers. Omit for the authenticated user's own wagers.
eventNoOnly wagers on this event id.
limitNoWagers per page, 1 to 20 (default 20).
activeNotrue: only open wagers (status purchased). Omit for no status filter. Cannot be combined with past_bets.
offsetNoNumber of wagers to skip, for paging (default 0, maximum 10000).
followingNotrue: only wagers by users you follow. Only works together with `event`.
past_betsNotrue: only finished wagers (status won, lost, sold or disabled). Omit for no status filter. Cannot be combined with active.
currency_modeNoplay_money = OOM wagers, real_money = USDC/USDT/USD wagers, all = both (default).all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses result ordering (newest first), the default scope (authenticated user), the status vocabulary, and the field set returned. It stops short of discussing auth requirements or rate limits, so it is strong but not exhaustive.

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?

The key scoping and paging facts are front-loaded, and the sentence on field contents substitutes for a missing output schema. The listing of returned fields is dense but earns its place since no output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 8 optional parameters and no output schema, the description covers return shape, page size, ordering, status meanings, and where to go for detail. It omits edge behaviors such as the offset cap or how `following` interacts with `event`, which the schema handles.

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 baseline is 3; the description goes further by explaining what `active` and `past_bets` mean in status terms and that results default to the caller's own wagers. The remaining filter semantics (event, following, currency_mode) are left to the schema.

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?

The description opens with a specific verb and resource ("Lists wagers (positions)") plus scope and ordering, and it explicitly points to get_wager_details for per-wager history, so an agent can distinguish it from that sibling without opening either 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 gives concrete selection rules: use `active` for open positions, `past_bets` for settled ones, and defer to get_wager_details when purchase and sale history is needed. The mutual exclusion of active/past_bets is reinforced, leaving little to infer.

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