GridIron Data

NFL bye weeks

get_byes

Read-onlyIdempotent

Returns every team's bye week for a season, and the teams on bye each week. Use it to plan lineups and spot bye-week holes on a roster. Basic plan and above.

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

Input Schema

Name	Required	Description	Default
`season`	No	Season year, 2020 or later. Default: the current season.

Output Schema

Name	Required	Description
`byes`	No	Team code -> bye week.
`note`	No	A sentence for the user saying which plan is needed.
`error`	No	Present only when the call failed: what went wrong.
`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.
`by_week`	No	Week -> teams on bye.
`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/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a genuine behavioral constraint not present in structured fields — "Basic plan and above" — which flags a subscription/access gate the agent should anticipate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: what it returns, why to use it, and the plan requirement. The return shape is front-loaded and nothing is repeated or padded.

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?

For a single optional-parameter, read-only tool with rich annotations and an output schema, the description covers purpose, use case, and access tier — enough to call it correctly. Return-value details are rightly omitted since an output schema exists.

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?

With one parameter at 100% schema description coverage, the schema already documents the season year, its regex format, default, and examples. The description adds no syntax or semantics beyond that, 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?

States a specific verb and resource ("Returns every team's bye week for a season") and even clarifies the shape is bidirectional ("and the teams on bye each week"). It doesn't name or contrast a sibling, but no sibling in the list covers bye weeks, so the resource itself disambiguates.

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?

Gives concrete usage context — "plan lineups and spot bye-week holes on a roster" — which tells the agent when this data matters. It stops short of stating exclusions or pointing at alternatives, so it falls just below the explicit when/when-not bar.

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?