GridIron Data

Request a news refresh for a player

request_news_scrape

Idempotent

Queues an on-demand news pull for a player who has no news coverage yet and returns at once (202); the headlines appear in get_player_news shortly after. Use it only when get_player_news comes back empty. Asking twice is harmless. 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": "request_news_scrape"
  }
}

Input Schema

Name	Required	Description	Default
`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.
`poll`	No	How to check for the result.
`error`	No	Present only when the call failed: what went wrong.
`reason`	No	Machine-readable failure reason, e.g. basic_required or pro_required.
`status`	No	Request status.
`message`	No	What happens next.
`player_id`	No	GridIron player id.
`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/5.0

Behavior4/5

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

The annotations already declare non-read-only, idempotent, non-destructive behavior, and the description adds useful async semantics: it returns at once with 202 and results appear later in get_player_news. It also states the Basic plan prerequisite, though it does not detail failure modes or rate limits.

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 short, front-loaded, and structured around the action, timing, correct usage, idempotency, and plan requirement. Every sentence adds relevant information.

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 one-parameter queueing tool with an output schema and rich annotations, the description covers the key operational context: async return, where results appear, when to use it, idempotency, and plan eligibility.

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 description coverage is 100%, with player_id format, examples, and a search_players fallback already documented. The description adds no further parameter meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific action and resource: queues an on-demand news pull for a player. It distinguishes the tool from get_player_news by explaining that this queues a refresh while headlines appear in get_player_news shortly after.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit gating condition: use only when get_player_news comes back empty. It also names the alternative and notes that asking twice is harmless, so an agent has clear when-to-use guidance.

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?