Skip to main content
Glama

Ball Ranks Fantasy Sports

Get weekly football rankings

get_week_rankings
Read-onlyIdempotent

Return published weekly fantasy football rankings for one position, week, and scoring format. Each row has the player, rank, and projected points. Use it for a ranked list or a start/sit comparison. Basketball is not available.

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": {
      "week": "<week>"
    },
    "name": "get_week_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekYesNFL week number, from 1 to 18.
limitNoMaximum number of players to return, from 1 to 100. Defaults to 50.
modelNoBall Ranks model. v0 is public and the default. v1 requires Premium.v0
sportNoFantasy sport. Weekly rankings are football only, so this defaults to football.football
offsetNoNumber of players to skip before this page. Defaults to 0.
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.
positionNoFootball position to rank: QB, RB, WR, TE, K, or DST. Defaults to RB.RB
scoring_formatNoFootball scoring format: standard, half_ppr, or ppr. Defaults to ppr.ppr

Output Schema

NameRequiredDescriptionDefault
metaYes
queryYes
totalYes
rankingsYes
sourceUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changed
    • addedInput schema / description
      Added value: +"Filters for one week of published fantasy football rankings."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of players to return, from 1 to 100. Defaults to 50."
    • addedInput schema / properties / limit / examples
      Added value: +[
      +  50
      +]
    • 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 / offset / description
      Added value: +"Number of players to skip before this page. Defaults to 0."
    • addedInput schema / properties / offset / examples
      Added value: +[
      +  0
      +]
    • addedInput schema / properties / position / description
      Added value: +"Football position to rank: QB, RB, WR, TE, K, or DST. Defaults to RB."
    • addedInput schema / properties / position / examples
      Added value: +[
      +  "RB"
      +]
    • addedInput schema / properties / scoring_format / description
      Added value: +"Football scoring format: standard, half_ppr, or ppr. Defaults to ppr."
    • 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. Weekly rankings are football only, so this defaults to football."
    • addedInput schema / properties / sport / examples
      Added value: +[
      +  "football"
      +]
    • addedInput schema / properties / week / description
      Added value: +"NFL week number, from 1 to 18."
    • 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 / query / properties / position / description
      Added value: +"Football position: QB, RB, WR, TE, K, or DST."
    • addedOutput schema / properties / query / properties / position / examples
      Added value: +[
      +  "RB"
      +]
    • addedOutput schema / properties / query / properties / scoringFormat / description
      Added value: +"Football scoring format: standard, half_ppr, or ppr."
    • addedOutput schema / properties / query / 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 readOnly=true, idempotent=true, destructive=false and openWorld=true, so the safety profile is fully covered. The description adds only the qualifier 'published' and the row shape, the latter of which duplicates the output schema. It says nothing about the Premium gating on the v1 model, pagination behavior, or empty-result cases.

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 the tool returns before usage notes. The 'Each row has the player, rank, and projected points' sentence largely restates the output schema, which is minor waste against an otherwise tight description.

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?

An output schema exists so return values need not be explained, and the schema documents every parameter including defaults and enum meanings. What remains for the description, namely the scope and the intended use case, is present, making it complete for an eight-parameter read-only query tool.

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 eight parameters, including the v0/v1 model and Premium requirement, are already documented in the schema. The description names only week, position and scoring format at a high level and adds no semantics beyond what the schema states. 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 gives a specific verb and resource ('Return published weekly fantasy football rankings') plus the scoping dimensions (one position, week, scoring format). It is clearly distinct from a season-level or projection tool conceptually, but it never names or contrasts with the siblings get_season_rankings or get_player_projections, so the agent must infer the boundary.

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?

'Use it for a ranked list or a start/sit comparison' gives positive usage context. However, there is no when-not guidance and no routing to the sibling tools, and 'Basketball is not available' excludes a sport value rather than an alternative tool. Adequate but with clear gaps.

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.