GridIron Data

NFL schedule and scores

get_schedule

Read-onlyIdempotent

Returns the NFL regular-season schedule: week, home and away teams, kickoff time (UTC), status and final score, for a season, one week or one team (with that team's bye week). Use it for "who plays whom", kickoff times and results. Basic plan and above; Pro keys also get each game's betting line (spread_home, over_under, moneylines, implied team points).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_schedule"
  }
}

Input Schema

Name	Required	Description
`team`	No	Only this team's games (also returns its bye week). Team code, e.g. BUF or KC. LA/LAR, WSH/WAS and JAC/JAX are interchangeable.
`week`	No	Only this week, 1-18. Default: the whole season.
`season`	No	Season year, 2020 or later. Default: the current season.

Output Schema

Name	Required	Description
`note`	No	A sentence for the user saying which plan is needed.
`odds`	No	Below Pro only: a note that betting lines need Pro.
`team`	No	Team filter.
`week`	No	Week filter.
`count`	No	Games returned.
`error`	No	Present only when the call failed: what went wrong.
`games`	No	Per game: week, home, away, kickoff (UTC), status, final score, and odds on Pro.
`reason`	No	Machine-readable failure reason, e.g. basic_required or pro_required.
`season`	No	Season.
`source`	No	Data source.
`status`	No	HTTP status of the failed API call.
`bye_week`	No	The team's bye week (only when team is given).
`updated_at`	No	When the schedule was last refreshed.
`upgrade_url`	No	Where to see the plans.
`required_plan`	No	The plan that unlocks this data: basic or pro.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's real contribution is the access-tier disclosure: 'Basic plan and above', with Pro keys additionally receiving spread_home, over_under, moneylines, and implied team points. That tier-dependent response shape is behavior an agent cannot learn from the annotations or schema, though pagination and rate limits are not addressed.

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 dense sentences, front-loaded with the return payload before the filter modes and tier note. The 'Use it for ...' sentence partially re-states the opening clause, so it is efficient but not perfectly waste-free.

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?

With an output schema present, the description needn't document return shapes, yet it still names the key fields and flags the tier-gated betting fields. For a three-parameter, optional-all read tool with full annotation coverage, an agent has everything needed to call it correctly.

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%, with each parameter already documenting defaults, ranges, and code aliases, so the schema does the heavy lifting and a baseline 3 applies. The description's 'for a season, one week or one team' framing mostly restates those parameters, and the bye-week behavior it mentions for the team filter is already stated in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 ('Returns the NFL regular-season schedule') and then enumerates exactly what comes back: week, home/away teams, kickoff time in UTC, status, and final score. It also scopes the three filter modes (season, week, team) and notes the extra Pro-tier betting-line fields, which is enough to distinguish it from a narrower sibling like get_byes.

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 a concrete use case in quoted terms ('who plays whom', kickoff times, results) and clarifies that the team filter returns that team's bye week, which is a non-obvious usage detail. It stops short of naming an alternative tool or stating when not to use it, so it is clear context rather than full routing guidance.

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

All GridIron Data tools Inspect

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

Need Help?