Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Get my leaderboard ranking

get_user_ranking
Read-only

Returns the authenticated user's current Futuur leaderboard position so traders can see where they rank relative to others. Read-only and limited to the authenticated account.

Instructions

Returns the authenticated user's current position on the Futuur leaderboard as {ranking}. Use it when the user asks where they stand relative to other traders. Read-only; it only covers the authenticated user.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so 'Read-only' partly restates structured data. The genuinely additive part is the scope constraint, 'it only covers the authenticated user,' which tells the agent not to expect other users' ranks, plus the {ranking} return field. It still does not say what the ranking value means (position number vs. percentile) or whether it requires a live authenticated session.

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 short sentences with zero waste: purpose first, usage condition second, safety/scope third. Front-loaded and easy to scan.

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 zero-parameter read tool with no output schema, the description covers purpose, trigger, scope, and the returned field. Minor gaps remain around what the ranking represents and whether the leaderboard has a time window, but nothing essential to invoking it is missing.

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 no parameters (0 count, 100% coverage), so the baseline of 4 applies. The description is consistent with a parameterless call and does not invent inputs, though it also adds nothing about implicit scoping (leaderboard period, population) the agent might need to qualify the answer.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns the authenticated user's current position on the Futuur leaderboard') and even names the returned field, {ranking}. It does not explicitly name a sibling for contrast, but the resource is distinct from get_user_profile and get_user_bets, so an agent can route to it 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 an explicit trigger: 'Use it when the user asks where they stand relative to other traders.' That is a clear usage condition with no exclusions or named alternatives, which fits a zero-parameter read tool with no meaningful overlap surface.

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