Skip to main content
Glama

NFL Usage: Target, Carry & Red-Zone Shares

nfl_usage
Read-onlyIdempotent

Use this when the user asks about NFL usage: who gets the most targets or carries, target and carry shares, opportunity share, red-zone looks, or how a team's shares change without a teammate. Returns, by view: "league" (every player's season and recent shares, biggest roles first), "red_zone" (targets and carries from the opponent's 20 in), "team" (a team_id: its players' shares, the regulars who missed games and, with without_player_id, each player's shares with and without him). Without Keel Stats Pro the league view lists the five biggest roles, the red zone its season alone, and the team view is refused; account.held says so. Not for NBA usage: use stat_forecasts or rankings_and_ratings.

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": "nfl_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNo"league" (default), "red_zone" or "team" (default with a team_id).
seasonNoOptional season year. Defaults to the season in play.
team_idNoNumeric NFL team ID from search, for the team view.
without_player_idNoOptional, the team view: each player's shares with and without this teammate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses real operational behavior: the free-tier degradation (league view capped at five biggest roles, red-zone limited to season alone, team view refused) and that 'account.held' signals this. That gating detail is exactly the kind of context annotations cannot express; it stops just short of describing result ordering or size limits for paid league views.

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-loads the trigger sentence, then view behavior, then the paywall caveat, then the exclusion — a sensible order with no filler sentences. It is dense and the nested parenthetical enumerations take effort to parse, which keeps it from a 5.

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?

No output schema exists, so the description carries the return-shape burden, and it does so per view while also covering the tier restriction and the sibling boundary. For a four-parameter, three-mode tool this leaves no material gap an agent would need before calling it.

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 coverage is 100%, so the baseline is 3, but the description earns more by explaining what each view actually yields — red_zone means targets/carries from the opponent's 20 in, and without_player_id produces each player's shares with and without that teammate. It also ties team_id to the team view, adding intent the schema only states flatly.

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 pairing ('NFL usage: who gets the most targets or carries, target and carry shares, opportunity share, red-zone looks') and enumerates the three views it returns. It also names the domain boundary (not NBA usage) and points to specific siblings, so an agent can distinguish it without opening the schema.

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?

Opens with an explicit trigger ('Use this when the user asks about...') listing the exact question shapes it serves. It also gives a negative case with a named alternative ('Not for NBA usage: use stat_forecasts or rankings_and_ratings'), covering both when to use and when not to.

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