Skip to main content
Glama

LUMA NBA Impact Metrics

describe

Read-onlyIdempotent

What a table, column or metric MEANS: definition, unit, which way is good, stability, flags. Pass a table (players, games, box_game, box_season, arc_season, arc_live, loki, loki_release, onoff_season, lineups, wowy, channels, xpts_rapm, player_seasons, pac_season, skills_season) or a metric id (e.g. sk_playmaking, ocreated, o_sel_rim, xq_d). Pass nothing for the conventions (units, seasons, sample sizes).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableNo
columnNo
metricNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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. The description adds useful behavioral context by listing the semantic information returned for each kind of input, including units, stability, and flags, which is more than the annotations provide.

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 description is front-loaded with the core meaning, followed by practical input examples and the no-argument case. The long parenthetical table list is dense but arguably earns its place as an inline enumeration; the sentence structure is compact despite the length.

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 a simple optional-parameter lookup with no output schema, the description covers the purpose, most input forms, and the kinds of information returned. It remains incomplete on column semantics, parameter combination rules, and the shape of the returned definitions, which an agent may need in order to invoke it confidently.

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 carries the burden and does explain what the table and metric parameters accept, including concrete table names and metric id examples. The column parameter is named but never given an example or format, and the description does not explain whether table, column, and metric can be combined or how conflicts are resolved.

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 states that this tool explains what a table, column, or metric means, and it enumerates the semantic fields returned (definition, unit, directionality, stability, flags). It is easy to distinguish from data-retrieval siblings, though it does not explicitly differentiate itself from interpretive siblings such as explain or docs.

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?

It gives concrete invocation guidance: pass a table name or metric id, or pass nothing for conventions. However, it does not say when to use this instead of explain, docs, or read_doc, nor does it state exclusion conditions.

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