GridIron Data

Search players by name

search_players

Read-onlyIdempotent

Finds players by full or partial name (case-insensitive) and returns each match's exact player_id ("First Last#POS"), team and position. Use it first whenever you have a name but not the id the other tools need. Defenses match by team code or nickname too ("TB", "Bucs", "Tampa Bay DST"). Free plan.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Full or partial player name, case-insensitive. For a defense, a team code or nickname works ("TB", "Bucs", "Tampa Bay DST").
`position`	No	Only this position.

Output Schema

Name	Required	Description
`note`	No	A sentence for the user saying which plan is needed.
`count`	No	Number of matches.
`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	HTTP status of the failed API call.
`players`	No	Matching players, each with its exact player_id.
`next_cursor`	No	Pass back as cursor for more matches; absent on the last page.
`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.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description adds value with the returned id format, case-insensitive/partial matching behavior, and the defense special case. "Free plan." gestures at a plan/quota constraint but is too terse to tell an agent what the limit actually is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core behavior and return shape, then the routing rule, then the defense edge case — a sensible order with no filler. The trailing fragment "Free plan." is under-specified and slightly ambiguous rather than economical.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still usefully previews the key returned field and its format, and it covers the defense-name edge case an agent would otherwise get wrong. The only real gap is the unexplained plan limitation, which is minor for a read-only search.

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%, so both parameters are already documented, and the description's notes on partial/case-insensitive matching and defense team codes largely restate the `name` schema description. The `position` filter is never mentioned in the description at all, so no meaning is added beyond the schema.

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 (finds players) plus the matching semantics (full or partial name, case-insensitive) and the return payload (exact player_id in "First Last#POS" form, team, position). That is enough to distinguish it from the id-based siblings like get_player_by_espn_id and get_player_by_gsis_id without opening their schemas.

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?

"Use it first whenever you have a name but not the id the other tools need" is explicit routing guidance that establishes this as the resolution step before id-based tools. It stops short of naming specific alternatives or stating when-not-to-use (e.g., when you already hold an id), so it is strong but not exhaustive.

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?