Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Get my balances

get_balances
Read-only

Retrieve the authenticated user's ledger balances by currency to check available funds before placing a bet or confirm holdings; optionally filter to one currency.

Instructions

Returns the authenticated user's ledger balances as a list with one {currency, amount} row per currency, for example OOM (play money) and USDC (real money). Use it before placing a bet to check the user can afford it, or to answer how much the user holds. Pass currency to get just that one row. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
currencyNoOnly return the balance in this currency code, matched case-insensitively (e.g. OOM, USDC, USDT, USD). Omit for every currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.1/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 trailing 'Read-only.' is largely confirmatory rather than new information. The description does add real behavioral context the annotations lack: it operates on the 'authenticated user' (no user parameter required) and returns a per-currency list rather than a single scalar. Pagination, ordering, and rate limits are unaddressed.

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?

Three short sentences, front-loaded with what is returned before the usage advice and the filtering hint. The trailing 'Read-only.' is the only near-redundant fragment given readOnlyHint is already set, but it costs almost nothing.

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?

There is no output schema, so the description carries the return-value burden and does so by naming the row shape and example currencies. Combined with a fully documented single optional parameter and explicit readOnly/openWorld annotations, the only minor gap is failure behavior (e.g., unknown currency code or empty ledger).

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 description coverage is 100% and the single `currency` parameter already documents case-insensitive matching and 'Omit for every currency'. The description's 'Pass `currency` to get just that one row' restates the filter outcome but adds no new syntax or format detail, so this sits at the baseline.

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?

Specific verb and resource ('Returns the authenticated user's ledger balances') plus the exact return shape ('one {currency, amount} row per currency'), with concrete examples (OOM play money, USDC real money). An agent can distinguish this from sibling tools like get_user_profile or list_orders without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives two concrete triggers: 'Use it before placing a bet to check the user can afford it, or to answer how much the user holds', which routes it relative to place_bet. It does not state when to use a different balance-adjacent tool or what to do on an empty/zero balance, so it stops short of a full when/when-not map.

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