Skip to main content
Glama

Ball Ranks Fantasy Sports

Get a player's projection

get_player_projections
Read-onlyIdempotent

Look up one player's published projection by player id or slug. Use scope season for a basketball or football season projection. Use scope weekly with a week number for one football week. Basketball has no weekly projection.

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

Input Schema

NameRequiredDescriptionDefault
weekNoNFL week number, from 1 to 18. Required when scope is weekly.
modelNoBall Ranks model. v0 is public and the default. v1 requires Premium.v0
scopeNoProjection window. season is the default. weekly is football only and requires week.season
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
weekNo
scopeYes
playerYes
seasonYes
sourceUrlYes
projectionYes
scoringFormatNoFootball scoring format: standard, half_ppr, or ppr.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changed
    • addedInput schema / description
      Added value: +"Identifies the player and the season or weekly projection 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 / scope / description
      Added value: +"Projection window. season is the default. weekly is football only and requires week."
    • addedInput schema / properties / scope / examples
      Added value: +[
      +  "season"
      +]
    • 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"
      +]
    • addedInput schema / properties / week / description
      Added value: +"NFL week number, from 1 to 18. Required when scope is weekly."
    • addedInput schema / properties / week / examples
      Added value: +[
      +  4
      +]
    • 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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only the domain constraint that basketball lacks weekly projections, which the schema's own scope description already states, and says nothing about what happens for unpublished seasons or the Premium model tier.

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?

Four short sentences, front-loaded with the purpose before the scope rules, with no filler or hedging. Slight redundancy with the schema's scope description is the only waste.

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 no explanation, and the full schema covers all parameters; the description supplies the sport/scope interaction that matters most for correct invocation. It could still say more about the Premium model tier and unpublished-player behavior, but nothing essential is missing.

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 every one of the seven parameters is already documented, including week bounds, model tiers, season formats and scoring_format defaults. The description restates the scope semantics without adding format, default or error-handling detail beyond the schema, 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?

The description opens with a specific verb and resource ('Look up one player's published projection') and names the identifier form (player id or slug), which separates it from the ranking siblings. It stops short of explicitly contrasting with get_player_rankings and friends, but the noun 'projection' does most of that work.

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?

It gives concrete routing rules for the scope parameter: season for basketball or football, weekly plus a week number for football only, and states plainly that basketball has no weekly projection. It does not address when to prefer this tool over the ranking siblings or what to do when a projection is unpublished.

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.