Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Get my profile

get_user_profile
Read-only

Retrieve the authenticated user's account details—identity, KYC/email status, real-money API eligibility, wager counts, settings, and per-currency wallet balances.

Instructions

Returns the authenticated user's own account: id, username, email, email and KYC status, whether real-money trading is enabled for the public API (public_api_real_money_enabled), wager counts, trading-relevant settings and a wallet object with the balance in each currency. Use it to answer who the user is, whether real money can be traded through the API, or for a quick balance snapshot; use get_balances to read one currency's balance. 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_user_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.6/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, and the description corroborates with 'Read-only' rather than contradicting it. Beyond the annotations it discloses scope (own account only, requires an authenticated session) and the identity of key returned flags such as public_api_real_money_enabled and KYC status. It does not mention error behavior for unauthenticated calls, which is the only notable gap.

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?

Two sentences, front-loaded with what is returned and followed by when to use it. The field enumeration is long but each item (KYC status, real-money flag, wallet balances) is decision-relevant to an agent; the phrase 'email, email and KYC status' is slightly clumsy wording that could be tightened.

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, so the description must carry the return-value burden, and it does so by naming the fields and the nested wallet object with per-currency balances. Combined with the annotation-covered safety profile and the get_balances pointer, an agent has everything needed to select and call this tool correctly.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline for a 0-param tool applies. The description correctly avoids inventing parameter talk and instead spends its words on return contents.

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 uses a specific verb and resource ('Returns the authenticated user's own account') and enumerates the returned fields (id, username, email, KYC status, public_api_real_money_enabled, wager counts, settings, wallet balances). It explicitly scopes the tool to the caller's own account, distinguishing it from tools that read other users' data, and names get_balances as the narrower alternative.

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 states concrete use cases ('answer who the user is, whether real money can be traded through the API, or for a quick balance snapshot') and explicitly routes the single-currency case to get_balances. When-to-use and when-to-prefer-a-sibling are both present, leaving nothing to inference.

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