Skip to main content
Glama

LUMA NBA Impact Metrics

player

Read-onlyIdempotent

One-stop player profile for a season (owner 2026-10-25: show everything). ARC 2-season and 1-season (net, O, D, shot value SV, possession value PV), the full SV / PV tree (selection, conversion, retention, generation, O and D), SV by zone, ARC individual-skill view (a separate slicing of the same total), PAC, xPTS-RAPM, creation lens, top skills, LOKI, raw on/off, top WOWY partners, box score. Default season = the last full season until about the All-Star break of the season in progress (the response says so); pass season for the current one (2027 = 2026-27).

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

Input Schema

NameRequiredDescriptionDefault
playerYesname or pid
seasonNoend year, e.g. 2026 = 2025-26

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 lookup. Beyond that, the description discloses the broad returned content and the important default-season behavior, including that the response indicates the default and that the current season must be passed explicitly.

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 purpose is front-loaded, but the description becomes a long, dense catalogue of abbreviations and metric names with little grouping. The internal owner-date parenthetical and 'the response says so' add noise, and terms like SV/PV and ARC are not fully explained.

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, so the description carries the burden of describing what comes back. It does enumerate the major output areas and explains the default-season behavior, though it gives little sense of response structure or field-level detail.

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 basic parameter definitions are already present. The description adds material meaning beyond the schema by explaining the default-season rule and clarifying that 2027 corresponds to the 2026-27 season.

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 clearly identifies a comprehensive player-season profile and enumerates the major included areas such as ARC, SV/PV, PAC, xPTS-RAPM, LOKI, WOWY partners, and box score. The 'show everything' framing helps distinguish it from narrower siblings like wowy, onoff, or game_log, though it does not use a direct verb.

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 'one-stop' and 'show everything', suggesting this is the broad profile tool rather than a focused sibling. The description adds useful season-default guidance, but it does not explicitly state when to choose this over compare, game_log, or wowy.

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