Skip to main content
Glama

NFL power rankings

invoke_nfl_power_rankings
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. BankrollSZN NFL power rankings for the current season: all 32 teams ranked by net EPA per play (offense EPA per play minus defense EPA per play allowed), with record, points for and against, point differential, offense and defense EPA ranks, a tier label, preseason rating and wins, and the rank the week before. Updated weekly after the games.

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

Input Schema

NameRequiredDescriptionDefault
teamNoTeam abbreviation.
limitNoMaximum rows to return. The plan limit applies on top.
offsetNoPaid plans: next page offset from page.next_offset.
sort_byNoDefault rank.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety bar is low; the description adds real context on top by disclosing an approval prompt on the first call, weekly refresh cadence, and that a plan limit caps rows. It doesn't mention rate limits or error behavior, but the disclosed approval gate and freshness are the traits an agent most needs.

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?

Two sentences with no filler, and the full metric definition and returned-field list earn their space. The approval note is placed before the actual purpose, which slightly buries the front-loaded 'what it does' statement, but nothing is redundant.

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?

There is no output schema, so the description carries the return-value burden and does so thoroughly, listing record, points for/against, differential, EPA ranks, tier, preseason rating, and prior-week rank. Combined with pagination/limit notes and the weekly-update cadence, an agent has everything needed to call and interpret it.

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 the parameters are already documented and baseline 3 applies. The description contributes indirect meaning by explaining what rank and the prior-week rank mean (relevant to sort_by's rank_change), but adds nothing about team abbreviation format, offset/limit interaction, or sort direction.

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 (NFL power rankings for the current season) and defines the ranking metric precisely: net EPA per play, computed as offense EPA per play minus defense EPA per play allowed. It also enumerates the returned fields, so an agent can tell it apart from sibling stats tools like invoke_nfl_elo or invoke_nfl_dvp without opening schemas.

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?

Usage is implied by scope statements ('current season', 'updated weekly after the games'), which tells the agent this is the current-week snapshot rather than historical data. However, it never says when to pick this over related siblings (e.g., EPA or team-stack tools) and gives no exclusions or prerequisites beyond the approval note.

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