Skip to main content
Glama

Ball Ranks Fantasy Sports

Get a player's season ranking

get_player_rankings
Read-onlyIdempotent

Look up one player's published season ranking by player id or slug. Returns that player's rank on the season board, including position rank and projected points when football publishes them.

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": {
      "sport": "<sport>",
      "player": "<player>"
    },
    "name": "get_player_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoBall Ranks model. v0 is public and the default. v1 requires Premium.v0
sportYesFantasy sport: basketball or football.
playerYesBall Ranks player id or slug.
seasonNoPublished season. Omit it to use the current season. Football uses the season year, such as 2026. Basketball uses a label such as 2026-27.
scoring_formatNoFootball scoring format: standard, half_ppr, or ppr. Football uses ppr when this is omitted. Leave it out for basketball.

Output Schema

NameRequiredDescriptionDefault
metaYes
playerYes
seasonYes
rankingYes
sourceUrlYes
scoringFormatNoFootball scoring format: standard, half_ppr, or ppr.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • addedInput schema / description
      Added value: +"Identifies the player whose published season ranking to look up."
    • addedInput schema / properties / model / description
      Added value: +"Ball Ranks model. v0 is public and the default. v1 requires Premium."
    • addedInput schema / properties / model / examples
      Added value: +[
      +  "v0"
      +]
    • addedInput schema / properties / player / description
      Added value: +"Ball Ranks player id or slug."
    • addedInput schema / properties / player / examples
      Added value: +[
      +  "victor-wembanyama"
      +]
    • addedInput schema / properties / scoring_format / description
      Added value: +"Football scoring format: standard, half_ppr, or ppr. Football uses ppr when this is omitted. Leave it out for basketball."
    • addedInput schema / properties / scoring_format / examples
      Added value: +[
      +  "ppr"
      +]
    • addedInput schema / properties / season / description
      Added value: +"Published season. Omit it to use the current season. Football uses the season year, such as 2026. Basketball uses a label such as 2026-27."
    • addedInput schema / properties / season / examples
      Added value: +[
      +  "2026-27",
      +  2026
      +]
    • addedInput schema / properties / sport / description
      Added value: +"Fantasy sport: basketball or football."
    • addedInput schema / properties / sport / examples
      Added value: +[
      +  "football"
      +]
    • addedOutput schema / properties / meta / properties / sport / description
      Added value: +"Fantasy sport: basketball or football."
    • addedOutput schema / properties / meta / properties / sport / examples
      Added value: +[
      +  "football"
      +]
    • addedOutput schema / properties / scoringFormat / description
      Added value: +"Football scoring format: standard, half_ppr, or ppr."
    • addedOutput schema / properties / scoringFormat / examples
      Added value: +[
      +  "ppr"
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safe read profile (readOnly, idempotent, non-destructive). The description adds useful domain context: only 'published' rankings are returned, and position rank and projected points appear only 'when football publishes them,' signaling possibly partial results. It does not address the Premium-gated v1 model or any error/empty-result behavior.

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 tight sentences with no filler, front-loading the operation and following with the return shape. 'Season ranking'/'season board' is slightly repetitive but earns its place as the scope qualifier.

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?

An output schema exists, so return values need not be enumerated, and the parameter schema is fully described. The description covers what makes this tool non-obvious (single-player scope, published-only data, football-conditional fields), leaving only the model/Premium distinction unaddressed, which the schema already handles.

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%, so all five parameters (including model, season format, and scoring_format defaults) are already documented. The description's only parameter reference, 'player id or slug,' restates the schema rather than adding format or constraint detail, so baseline 3 applies.

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 ('Look up one player's published season ranking') and scopes it to a single player, which implicitly separates it from the plural-board sibling get_season_rankings. It never names an alternative explicitly, so sibling differentiation is only implied.

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

Usage Guidelines3/5

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

The phrase 'by player id or slug' tells the agent what to supply, and 'one player' implies this is the per-player lookup rather than a board listing. There is no explicit when-to-use/when-not guidance and no named alternative for retrieving full season boards.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.