Skip to main content
Glama

Ball Ranks Fantasy Sports

Get season rankings

get_season_rankings
Read-onlyIdempotent

Return one page of a published Ball Ranks season ranking board. Basketball results are nine-category, per-game rankings. Football results are projected points for standard, half-PPR, or PPR scoring.

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>"
    },
    "name": "get_season_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
sportYesFantasy sport: basketball or 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.
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
queryYes
totalYes
rankingsYes
sourceUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changed
    • addedInput schema / description
      Added value: +"Filters for one page of a published season ranking board."
    • 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 / 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 / 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
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds valuable semantics beyond that: results are paged ("one page"), basketball is nine-category per-game rankings, and football is projected points keyed to a scoring format. It stops short of noting that unpublishing or model gating can make a board unavailable.

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 the core action and resource, with no filler. The two sport-semantics sentences carry real information rather than restating the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, one required, and an output schema present, the definition does not need to describe return values, and it gives useful sport-specific result semantics. It is still thin on operational context: nothing about pagination termination, the Premium gate on model v1, or the fact that only published boards are reachable.

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 limit, offset, model, season and scoring_format are already documented with enums, defaults and sport-specific formats. The description reinforces sport-dependent result meaning and paging ("one page") but adds no parameter-level detail such as page-size limits or how to detect the final page, so the 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?

"Return one page of a published Ball Ranks season ranking board" gives a specific verb and resource, and the two follow-up sentences define what the results actually are for each sport. It does not explicitly contrast itself with week or player rankings siblings, so an agent must infer the season scope distinction from the word "season".

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?

Usage is implied by "season ranking board" and "one page", so an agent can tell this is for paginated full-season boards rather than weekly or per-player lookups. However, there is no explicit when-to-use statement, no mention of when to prefer get_week_rankings or get_player_rankings, and no prerequisites such as the Premium requirement for model v1.

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.