GridIron Data

Snap share and role trend

get_snap_share

Read-onlyIdempotent

Returns a player's offensive snap share each week (the % of his team's offensive plays he was on the field for), the season average, and a trailing average with its change vs the season. Use it to spot role changes before they show in the box score (a committee back taking over, a rookie WR passing a veteran). Seasons 2020-2026, current season updated weekly. Basic plan and above.

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": {
      "player_id": "<player_id>"
    },
    "name": "get_snap_share"
  }
}

Input Schema

Name	Required	Description
`trend`	No	Weeks in the trailing average compared with the season, 1-18.
`season`	No	Season year, 2020 or later. Default: the current season.
`player_id`	Yes	GridIron player id, "First Last#POS", matched case-insensitively. Defenses are "Team Name#DST". Unsure of the id? Call search_players first.

Output Schema

Name	Required	Description
`note`	No	A sentence for the user saying which plan is needed.
`team`	No	Current team code.
`error`	No	Present only when the call failed: what went wrong.
`games`	No	Games on the schedule so far.
`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.
`totals`	No	Season snap totals.
`position`	No	Position.
`player_id`	No	GridIron player id ("First Last#POS").
`player_name`	No	Player name.
`trend_delta`	No	Recent average minus season average (positive = growing role).
`trend_weeks`	No	Weeks in the trailing average.
`upgrade_url`	No	Where to see the plans.
`weekly_snaps`	No	Per week: snaps and snap share.
`required_plan`	No	The plan that unlocks this data: basic or pro.
`games_with_snaps`	No	Games he played offensive snaps in.
`recent_snap_pct_avg`	No	Average over the trailing trend weeks.
`season_snap_pct_avg`	No	Season average snap share (0-100).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real context beyond them: coverage window (2020–2026), update cadence ('current season updated weekly'), and an access-tier constraint ('Basic plan and above'). It does not discuss missing-data behavior for players with no snaps, which keeps it from a 5.

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 sentences, front-loaded with the return value, then the decision-relevant use case, then coverage and plan constraints. Nothing is padded and every clause carries information an agent cannot get from structured fields.

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 restate return shape, and it still discloses the data window, refresh cadence, and plan gating. Annotations and full schema coverage handle the rest, so an agent has everything needed to call this 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 coverage is 100% and already documents player_id format, the season pattern/default, and the trend range of 1–18. The description's phrase 'a trailing average with its change vs the season' adds conceptual grounding for what trend controls but no format or edge-case detail beyond the schema, so the baseline 3 applies.

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 definition names a specific verb and resource — 'Returns a player's offensive snap share each week' — and enumerates the three outputs (weekly share, season average, trailing average with change). The parenthetical defining snap share as '% of his team's offensive plays he was on the field for' makes it unmistakable versus stat-oriented siblings like get_player_stats.

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 when-to-use framing: 'Use it to spot role changes before they show in the box score,' reinforced with two named scenarios (committee back taking over, rookie WR passing a veteran). It stops short of naming an alternative tool or stating when not to use it, so it falls one step below the explicit routing 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?