Skip to main content
Glama

LUMA NBA Impact Metrics

onoff

Read-onlyIdempotent

Raw on/off splits for a player across seasons: team ratings and shot diet with him on vs off (games he played) plus the NBA.com-style tenure version. Unadjusted -- depends on teammates and opponents. season = one season; or from_season / to_season. No possession minimum: check on_poss / off_poss.

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

Input Schema

NameRequiredDescriptionDefault
playerYes
seasonNo
to_seasonNo
from_seasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuine context beyond them: results are unadjusted, are confounded by teammates and opponents, and impose no possession minimum so small samples are possible. It stops short of describing return shape or ordering, which matters given there is no output schema.

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?

Dense and front-loaded: what is returned comes first, then the statistical caveat, then parameter usage, then the sample-size warning. Telegraphic phrasing costs a little readability, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description names output fields (on_poss, off_poss) and the analytic caveats, which is valuable with no output schema. Still missing for a 4-parameter tool at 0% schema coverage: the expected player identifier format and the season numbering convention, both of which an agent needs to call correctly.

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 0%, so the description must carry the load. It does explain the season vs from_season/to_season choice ('season = one season; or from_season / to_season'), which is the key ambiguity, but leaves the 'player' parameter's expected format (name vs id) and the season integer encoding unstated.

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?

States a specific resource ('raw on/off splits for a player across seasons') and enumerates the content returned: team ratings, shot diet on vs off, plus an NBA.com-style tenure variant. It does not explicitly distinguish itself from the adjacent 'wowy' sibling, which is the nearest conceptual neighbour, so it falls short of a 5.

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 through the caveat 'Unadjusted -- depends on teammates and opponents' and the warning to check sample size via on_poss/off_poss, which tells an agent when the numbers are trustworthy. However, there is no explicit statement of when to pick this over 'wowy' or 'player', and no prerequisites are given.

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