Skip to main content
Glama

LUMA NBA Impact Metrics

leaderboard

Read-onlyIdempotent

Ranked list from one source. source: arc_season | arc_live | loki | loki_release | onoff_season | box_season | xpts_rapm | pac_season | skills_season (e.g. sk_switchability_pct) | channels (metric = a metric id from describe, e.g. sk_playmaking, ocreated, xq_d; window 1-5, LOKI channels have one value per season). metric must be a column of that source. Filters: season, window (arc_season 1-5), release (loki R1-R4, or weekly for the in-progress season; default R1, newest for the in-progress season), min_poss, pos (G/W/B), team, per (box_season: total|per_game).

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": {
      "source": "<source>"
    },
    "name": "leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
perNo
posNo
teamNo
limitNo
metricNo
seasonNo
sourceYes
windowNo
releaseNo
min_possNo
ascendingNo

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?

Annotations already declare this a read-only, idempotent, closed-world operation, so the description does not need to argue safety. It does add genuine behavioral context beyond them: per-source semantics (channels carry one value per season, LOKI release defaults to R1 with newest for the in-progress season, arc_season window 1-5). It omits sorting/pagination behavior despite having limit and ascending parameters, which keeps it from 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?

The core statement is front-loaded and the dense parameter notes are packed into two sentences, which is efficient for an 11-parameter tool. It reads as a run-on reference block with the source enum restated at length, but each clause adds source-specific meaning rather than 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?

For an 11-parameter, zero-schema-coverage, no-output-schema tool, the description covers most filter semantics but leaves limit and ascending undocumented and says nothing about ordering defaults or result size. An agent could call it, but could not predict how much data comes back or how to page through a large ranking.

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 description coverage is 0%, so the description carries the full burden and largely meets it: it explains source-specific meaning of metric and window, the release default and accepted range, pos values as G/W/B, and per as total|per_game for box_season. Two parameters, limit and ascending, are never mentioned, and team/season formats are left implicit, so it falls short of complete.

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?

Opens with a concrete statement of the output shape and scope: 'Ranked list from one source.' That tells an agent exactly what it gets back and that it is single-source, which is enough to distinguish it from a multi-entity sibling like compare. It stops short of naming which sibling to use for multi-source or filtered player lookups, so a 4 rather than 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 rather than stated: the agent can infer 'use this to get a ranking from source X,' and the note that 'metric must be a column of that source' plus the pointer to 'a metric id from describe' gives a real prerequisite workflow. There is no explicit when-not guidance and no named alternative for cases this tool does not fit.

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