GridIron Data

Injury status changes

get_injury_changes

Read-onlyIdempotent

Returns players whose injury status changed since a time (default the last 24 hours, up to 14 days back), with previous_status, status and detected_at. Statuses are checked against ESPN every 2 minutes from 8am to 1am ET. Use it for "who got hurt or cleared today?" and game-day checks; pass next_since back as since to get only newer changes. Pro plan (Free and Basic keys get 403 pro_required).

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

Input Schema

Name	Required	Description
`team`	No	Only this team. Team code, e.g. BUF or KC. LA/LAR, WSH/WAS and JAC/JAX are interchangeable.
`limit`	No	Maximum changes, 1-1000. Default 500.
`since`	No	Only changes after this time: ISO-8601 or unix seconds. Default: 24 hours ago; at most 14 days back. Pass a previous answer's next_since to get only newer changes.
`position`	No	Only this position.

Output Schema

Name	Required	Description
`note`	No	Present when since was clamped to the 14-day window.
`count`	No	Changes returned.
`error`	No	Present only when the call failed: what went wrong.
`since`	No	Start of the window.
`until`	No	End of the window.
`reason`	No	Machine-readable failure reason, e.g. basic_required or pro_required.
`season`	No	Season.
`status`	No	HTTP status of the failed API call.
`changes`	No	Per change: player, team, previous_status, status and detected_at.
`truncated`	No	true when more changes exist than limit allowed.
`next_since`	No	Pass back as since to get only newer changes.
`upgrade_url`	No	Where to see the plans.
`required_plan`	No	The plan that unlocks this data: basic or pro.
`team_freshness`	No	Per team: when its injury report was last checked and updated.
`last_checked_at`	No	When GridIron last checked injury statuses.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavior: a 2-minute polling cadence from 8am–1am ET, a default 24-hour window capped at 14 days back, and a Pro-only access gate returning 403 pro_required. Those are exactly the operational facts an agent needs and none are in the annotations.

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?

The output fields come first, followed by freshness cadence, use cases, cursor mechanics, and the plan gate — every sentence contributes a distinct fact with no filler or repetition.

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 and full schema parameter coverage, the description only needed to cover freshness, limits, cursor semantics, and access tier — all of which it does. Nothing an agent needs before calling is missing.

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 team/position/limit/since are already documented in the schema, including defaults and the 14-day cap. The description reinforces the since/next_since cursor chaining, but that is also spelled out in the schema, so added meaning is marginal beyond the baseline.

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?

"Returns players whose injury status changed since a time" names a specific verb and resource, and the description enumerates the returned fields (previous_status, status, detected_at). This clearly separates it from siblings like get_inactives or get_latest_news, which are snapshots/news rather than status deltas.

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 concrete usage framing ("who got hurt or cleared today?", game-day checks) and the incremental-polling pattern (pass next_since back as since). It does not explicitly name a sibling alternative or state when NOT to use it, so it falls short of a 5.

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?