Skip to main content
Glama

Player Splits, On/Off & Teammates (Pro)

player_splits_and_on_off
Read-onlyIdempotent

Use this when the user asks how a player's team does with him on or off the floor, his clutch or garbage-time splits, or how he plays with or without a teammate (NFL: target, carry and red-zone shares with or without a teammate). Returns those splits for the season (NBA: on/off, situations and milestones, detail naming the ones wanted; NFL: his usage row and the team's busiest, detail "full" for every player). Requires Keel Stats Pro; the answer says so when the account has none. Not for season averages or recent games: use player_profile.

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_splits_and_on_off"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNo"compact" (default), "full" (NFL: every player of the team's usage), or a comma-separated list of NBA sections: "on_off", "situations", "milestones".
leagueYesLeague ("nba" or "nfl").
seasonNoOptional season year. Defaults to the current season.
player_idYesNumeric player ID from the search tool.
teammate_idNoOptional numeric teammate player ID to drill into specific two-man / with-without splits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "\"compact\" (default), \"full\" (NFL: every player of the team's usage), or a comma-separated list of NBA sections: \"on_off\", \"situations\", \"milestones\".",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/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 bar is lower, and the description still adds real context: a Keel Stats Pro entitlement requirement, the fact that the response itself signals a missing subscription, and league-divergent return shapes. It stops short of describing relative cost or response size, which keeps it off a 5.

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?

Three sentences, front-loaded with the primary use case and ending with the routing exclusion, so nothing is buried. The heavy parenthetical nesting of league-specific behavior makes it dense to parse on first read but no sentence is filler.

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?

With no output schema and five parameters, the description carries the burden of explaining what comes back, and it does name the returned splits and league differences plus the entitlement failure mode. The exact shape of the on/off and milestone payloads is left implicit, which is the main remaining gap for a fairly complex tool.

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 every parameter including the `detail` enum is already documented in structured form; the description mostly restates the same detail semantics (sections for NBA, 'full' for every NFL player). It adds modest value by tying `detail` choices to league context, but not enough to exceed the baseline that full schema coverage establishes.

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?

Description names a specific resource and verb family: on/off splits, clutch or garbage-time splits, and with/without-teammate splits, with explicit league-specific rendering (NBA sections vs NFL target/carry/red-zone shares). It directly distinguishes itself from player_profile, so an agent can pick correctly 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 a concrete user-intent trigger ('when the user asks how a player's team does with him on or off the floor...'), and closes with an explicit exclusion plus the correct alternative ('Not for season averages or recent games: use player_profile'). Both when-to-use and when-not-to-use are present.

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