EndzoneAPI

get_plays

Read-only

Use for play-by-play with nflfastR metrics: EPA, WPA, win probability, success, CPOE, air yards, formation flags, and the players involved. Filter by game, or by season plus week/team/player, plus play type, down, quarter, win-probability band, red zone, third down. Set include_charting for FTN manual charting from 2022 on -- alignment, pre-snap motion, play action, screens, run-pass options, blitzer counts, drops -- or filter directly on those flags. Returns a per-query EPA and success-rate summary. Paginate with offset. Costs 10 credits.

Input Schema

TableJSON Schema

Name	Required	Description
`down`	No	Down
`week`	No	Week
`limit`	No	Max plays (default 200)
`is_rpo`	No	Charting filter: run-pass option (2022+)
`max_wp`	No	Maximum pre-play win probability
`min_wp`	No	Minimum pre-play win probability for the offense
`offset`	No	Pagination offset
`season`	No	Season year (required when game_id is not set)
`defteam`	No	Defense team code
`game_id`	No	Game id, e.g. 2025_01_KC_BUF
`is_drop`	No	Charting filter: charted drop (2022+)
`posteam`	No	Offense team code
`quarter`	No	Quarter (5+ = overtime)
`red_zone`	No	Only plays inside the 20
`is_motion`	No	Charting filter: pre-snap motion (2022+)
`passer_id`	No	GSIS id of the passer
`play_type`	No	Play type
`rusher_id`	No	GSIS id of the rusher
`third_down`	No	Only third downs
`receiver_id`	No	GSIS id of the receiver
`is_no_huddle`	No	Charting filter: no huddle (2022+)
`min_blitzers`	No	Charting filter: at least this many blitzers (2022+). FTN counts rushers beyond the base rush, so this is typically 0-3; 5+ is almost never charted.
`is_trick_play`	No	Charting filter: trick play (2022+)
`is_play_action`	No	Charting filter: play action (2022+)
`is_screen_pass`	No	Charting filter: screen pass (2022+)
`include_charting`	No	Attach FTN manual charting to each play (2022+): alignment, motion, play action, screens, RPO, blitzers, drops
`is_qb_out_of_pocket`	No	Charting filter: quarterback out of the pocket (2022+)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`plays`	Yes
`summary`	Yes
`next_offset`	Yes
`charted_plays`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral details beyond that: it returns a per-query EPA/success summary, requires pagination with offset, and costs 10 credits. It also notes the 2022+ limitation for FTN charting, which is valuable context.

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 description is compact yet information-dense, front-loading the tool's core purpose before listing filters and behavior. Every sentence earns its place, and it avoids redundant restatement of schema details.

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?

For a tool with 27 parameters and an output schema, the description covers the essential context: what the tool returns, how to filter, when charting data is available, how to paginate, and the credit cost. The output schema handles return-value details, so the description is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaning by grouping parameters into logical categories (game vs. season filters, charting flags, pagination) and by clarifying the win-probability band concept and player filters. This is more than the schema alone provides.

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 clearly states the tool is for play-by-play data with nflfastR metrics (EPA, WPA, CPOE, etc.), which is a specific verb+resource and distinct from siblings like get_advanced_stats or get_player_stats. It also enumerates available filters and features, leaving no ambiguity about what the tool does.

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?

The description gives clear context on when to use the tool: for play-by-play with advanced metrics, filtering by game or season/week/team/player. It does not explicitly name alternatives or state exclusions, but the 'Use for' phrasing effectively routes the agent to this tool for this purpose.

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

All EndzoneAPI 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.