Skip to main content
Glama

NFL player matchup card: what a defense allows to his position

invoke_nfl_player_matchup
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. NFL player matchup card, calculated by BankrollSZN. What one defense allows per game to the player's position group (QB, RB, WR or TE: PPR points, targets, receptions, yards, TDs; last 17 games) vs the league average, with rank (N = allows the most), next to the player's own per-game numbers, his last 5 games and his games against that team. Window: each defense's most recent games across seasons, so early-season samples are not tiny. No opponent = his next opponent on the slate. Example: player Ja'Marr Chase.

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": "<player>"
    },
    "name": "invoke_nfl_player_matchup"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerYesPlayer name.
opponentNoDefense abbreviation (MIA, TEN, LA). Default this week's opponent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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), so the remaining burden is low, and the description still adds real behavior: the first call triggers an approval prompt, the ranking convention is 'N = allows the most', and the sample window is each defense's most recent games across seasons so early-season samples aren't tiny. Those are non-obvious traits an agent would otherwise have to discover at runtime. It stops short of describing failure modes or result size/format.

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

Conciseness3/5

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

Substance is high but the delivery is a single dense block with stacked parentheticals and semicolons, which is harder to parse than a short bulleted breakdown. The lead sentence about first-call approval is placed before the tool's actual purpose, delaying the key information. Little of the content is filler, but the structure works against front-loading.

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?

There is no output schema, and the description does the work of explaining the return contents — opponent-allowed per-game stats versus league average, rank, the player's own per-game numbers, last 5 games, and games against that team. Combined with the sample-window and approval notes, an agent can predict what comes back. Missing only edge-case behavior for invalid players or missing opponents.

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%, so both parameters are already documented, and the description largely restates the schema's default-opponent behavior. It does add interpretation — the example player Ja'Marr Chase and the fact that the player's position group (QB/RB/WR/TE) determines what is compared — but gives no guidance on name format sensitivity or how to disambiguate similar names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource — an NFL player matchup card showing what one defense allows per game to the player's position group — and enumerates the exact metrics (PPR points, targets, receptions, yards, TDs, rank, last 5 games, head-to-head). That is far more specific than the title alone. It does not explicitly contrast itself with near siblings such as invoke_nfl_game_matchup or invoke_nfl_dvp, so an agent must infer the boundary from the word 'player' in the name.

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

Usage Guidelines3/5

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

Useful conditional guidance exists for the opponent parameter: 'No opponent = his next opponent on the slate.' That tells the agent it can omit the optional argument and still get a meaningful result. However, there is no statement of when to prefer this card over other matchup-oriented siblings, and no mention of what happens on an ambiguous or unmatched player name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources