Skip to main content
Glama

Player Profile & Advanced Stats

player_profile
Read-onlyIdempotent

Use this when the user asks about one player's season or recent form ('Tatum stats', 'how is Bridges playing lately'). Returns season averages, efficiency (NBA: TS%, eFG%, USG%, BPM; NFL: yards, touchdowns, EPA), Keel Impact, current injury status, (NBA) shot_contest: his shooting by the closest defender's distance and his shot defense against the league, his recent box lines (five without an account, ten signed in), NBA tracking (touches, drives, potential assists and rebound chances with what he made of them) and play types, NFL snap shares, the week's practice report and advanced stats with league ranks (his weeks against the close: a few without Pro) and, when the books have priced his next game, one compact row per stat as props_research gives it. With Keel Stats Pro, detail adds the book-by-book odds, closing lines, game log, history and alternate ladders. The answer's account.held names what the caller's plan left out. Not for on/off or teammate splits (player_splits_and_on_off).

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": {
      "league": "<league>",
      "player_id": "<player_id>"
    },
    "name": "player_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoKeel Stats Pro: "compact" (default), "full" (the long answer), or a comma-separated list of sections: "books", "ladders", "closes", "games", "history" (as in props_research).
leagueYesLeague ("nba" or "nfl").
seasonNoOptional season year (e.g. 2026 for 2025-26 NBA or 2025 NFL). Defaults to the current season.
player_idYesNumeric player ID from the search tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "Keel Stats Pro: \"compact\" (default), \"full\" (the long answer), or a comma-separated list of sections: \"books\", \"ladders\", \"closes\", \"games\", \"history\" (as in props_research).",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The annotations already establish that this is a safe read-only, idempotent, closed-world operation. The description adds meaningful behavioral context beyond that: plan-based limits on box lines, Pro-only `detail` sections, the `account.held` signal, and what content is returned for NBA versus NFL.

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?

The description is front-loaded with the usage condition, which helps, but the return-value portion is a dense run-on with nested parentheses and heavy jargon. Most clauses carry information, but the lack of structure hurts readability for an agent.

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 burden of explaining returns, and it does so extensively across NBA and NFL outputs, plan gating, and Pro detail. Given the tool's complexity, it is complete enough for an agent to understand what will be returned and what access limitations apply.

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%, and the schema already defines `league`, `player_id`, `season`, and `detail`. The description adds only limited extra meaning, mainly mapping `detail` to book odds, closing lines, game log, history, and ladders, which is close to what the schema already says.

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 opening sentence states the exact scope: one player's season or recent form, with concrete trigger examples like 'Tatum stats'. It also distinguishes the tool from player_splits_and_on_off, so an agent can identify the correct tool 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?

It gives explicit when-to-use examples and an explicit when-not exclusion for on/off and teammate splits, naming player_splits_and_on_off as the alternative. This is strong routing guidance rather than implied usage.

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