Skip to main content
Glama

LUMA NBA Impact Metrics

compare

Read-onlyIdempotent

Side-by-side comparison of 2-6 players for one season. source: all (default: ARC net / O / D / SV / PV, the SV / PV tree, SV by zone, individual-skill view, PAC, xPTS-RAPM, skills, LOKI, on/off, box in one answer) | arc_season | arc_svpv | arc_zones | arc_skill | pac_season | xpts_rapm | skills_season | loki_release | onoff_season | box_season. window = ARC window, default 2.

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": {
      "players": "<players>"
    },
    "name": "compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNo
sourceNo
windowNo
playersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds genuinely useful behavior context — the 2-6 player cap, single-season scope, and default window of 2 — but says nothing about what the response looks like when 11 data sources are merged 'in one answer'.

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 sentence is correctly front-loaded and efficient. The source clause then degenerates into a dense pipe-separated run-on of cryptic tokens, which is hard to parse and mixes prose description of 'all' with bare enum names.

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?

With no output schema, four parameters, and zero schema description coverage, the description should explain more. It covers player count and the window default adequately, and the source enumeration tells the agent which datasets exist, but the individual source tokens and the 'season' parameter remain undefined, and the shape of a multi-source comparison result is unstated.

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 has to carry the parameter burden. It partially does: it explains what the 'all' source aggregates and gives a default and meaning for 'window' ('ARC window, default 2'). But most enum values (arc_svpv, arc_zones, pac_season, xpts_rapm, loki_release, onoff_season, box_season) are opaque abbreviations with no gloss, and 'season' is left completely unexplained.

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 first sentence gives a concrete verb and resource: side-by-side comparison of 2-6 players within a single season. That scope is distinct from single-player tools like 'player' or pair-only tools like 'wowy', though the description never names those siblings explicitly to reinforce the distinction.

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 rather than stated: the 2-6 player range and 'for one season' signal when this tool fits, and calling out 'all' as the default with everything bundled 'in one answer' hints that most callers can skip source selection. However, there is no explicit when-to-use/when-not guidance and no routing to alternatives such as 'player' or 'wowy' for different comparison shapes.

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