Skip to main content
Glama
Sign In

Realtime Sports API

by io.github.ahunter135
OverviewDiscussionsAdmin

College rankings

get_rankings
Read-only

College polls: AP Top 25, coaches poll and (college football) the College Football Playoff rankings. Only football/college-football and basketball/mens-college-basketball. Latest release unless week is given.

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

Input Schema

NameRequiredDescriptionDefault
pollNoOne poll; default every poll.
weekNoA past week of the season.
sportYesSport slug.
leagueYesLeague slug. Monitored leagues (sport/league): football/nfl (NFL), football/college-football (College Football), basketball/nba (NBA), basketball/mens-college-basketball (Men's College Basketball), baseball/mlb (MLB), hockey/nhl (NHL), soccer/usa.1 (MLS), soccer/usa.open (U.S. Open Cup), soccer/eng.1 (Premier League), soccer/uefa.champions (Champions League), soccer/uefa.europa (Europa League), soccer/eng.fa (FA Cup), soccer/esp.1 (LaLiga), soccer/ita.1 (Serie A), soccer/mex.1 (Liga MX), soccer/fifa.world (World Cup), soccer/eng.w.1 (Women's Super League), soccer/uefa.wchampions (Women's Champions League), soccer/uefa.europa.conf (Conference League), soccer/eng.league_cup (League Cup), soccer/ger.1 (Bundesliga), soccer/fra.1 (Ligue 1), soccer/usa.nwsl (NWSL), soccer/eng.2 (Championship), soccer/fifa.worldq.uefa (WC Qualifying UEFA), soccer/fifa.worldq.conmebol (WC Qualifying CONMEBOL), soccer/fifa.worldq.afc (WC Qualifying AFC), soccer/fifa.worldq.caf (WC Qualifying CAF), soccer/fifa.worldq.concacaf (WC Qualifying CONCACAF). Call list_leagues if unsure.
seasonNoSeason year for week (college basketball 2026-27 = 2027).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety and data-source openness are covered. The description adds the useful defaults (latest release, all polls when poll is omitted), but says nothing about return shape, ordering, or whether a missing week's poll returns empty.

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 short sentences, front-loaded with the resource and followed by scope constraints; nothing is wasted. The parenthetical '(college football)' placement makes the second sentence slightly clunky but not confusing.

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 five parameters and no output schema, the description should at least hint at what a ranking record contains (rank, team, votes) and how multiple polls are returned when poll is omitted. It covers scope and defaults well but leaves the return value entirely unspecified.

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 coverage is 100%, so the schema already documents every parameter and both enums, giving a baseline of 3. The description does add a modest signal by narrowing the relevant league slugs out of the long list in the schema, but it does not explain poll, week, or season semantics beyond what the schema states.

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 names the concrete resource (AP Top 25, coaches poll, College Football Playoff rankings) and the two sport/league combinations it covers, so an agent can tell it is a rankings retrieval tool rather than a scores or odds tool among the siblings. It stops short of a clean verb+resource statement, but the scope is unmistakable.

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?

'Only football/college-football and basketball/mens-college-basketball' explicitly excludes the other sports and leagues the schema permits, which is real when-not-to-use guidance. 'Latest release unless week is given' explains the default behavior. What is missing is a named alternative for non-college rankings, though none exists among the siblings.

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

All Realtime Sports API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources