GridIron Data

Rest-of-season projections

get_ros_projections

Read-onlyIdempotent

Returns each player's projected fantasy points for the rest of the current season (weeks already played and his bye are skipped), with games_remaining and points_per_game. Use it for trades, waiver pickups and dynasty or keeper decisions. Filter by position, team or one player. 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_ros_projections"
  }
}

Input Schema

Name	Required	Description	Default
`team`	No	Only this team's players. Team code, e.g. BUF or KC. LA/LAR, WSH/WAS and JAC/JAX are interchangeable.
`scoring`	No	Fantasy scoring: ppr (full PPR, the default), half (half-PPR) or standard.	ppr
`position`	No	Only this position.
`player_id`	No	Only this player. 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	Team filter.
`count`	No	Rows returned.
`error`	No	Present only when the call failed: what went wrong.
`method`	No	How the totals are built.
`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.
`scoring`	No	Scoring used.
`position`	No	Position filter.
`method_note`	No	Notes on the method.
`projections`	No	Per player: projected points for the rest of the season, games_remaining and points_per_game.
`upgrade_url`	No	Where to see the plans.
`current_week`	No	The current NFL week.
`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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral context: played weeks and byes are excluded from the projection window, and access is gated to 'Basic plan and above' — an auth/tier constraint no structured field carries.

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 tight sentences: what it returns and the exclusion rule first, then use cases, then the plan gate. No filler, and the most load-bearing constraint (skipped weeks and byes) is front-loaded.

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?

An output schema exists, so return values need no further explanation, and the description still names the key fields. Combined with 100% schema coverage and full annotation set, an agent has everything needed to select and call this tool 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 each parameter is already documented in detail, including team-code aliasing, scoring enum, and player id format. The description's 'Filter by position, team or one player' merely restates what the schema says, adding no syntax or matching nuance, 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?

States a specific verb and resource ('Returns each player's projected fantasy points') plus a precise scope ('rest of the current season, weeks already played and his bye are skipped'). The rest-of-season scope implicitly separates it from the season-long sibling get_projections, and the named output fields (games_remaining, points_per_game) make the shape concrete.

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 clear use contexts — trades, waiver pickups, dynasty/keeper decisions — so an agent knows the decision class this feeds. It stops short of naming alternatives (e.g. 'for a single week use get_projections'), so no explicit exclusions or routing rules are provided.

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?