Skip to main content
Glama

LUMA NBA Impact Metrics

explain

Read-onlyIdempotent

Explain one LUMA term (e.g. "ARC", "LOKI", "shot value", "retention", "lineups", "Team FE", "cRAPM", "PAC", "p_top10"): the matching definitions from the agent docs plus any metric channels with that name. Use it when a user asks what something means.

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": {
      "term": "<term>"
    },
    "name": "explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that results are merged from two sources (agent docs definitions and metric channels), which is genuinely useful behavioral detail, but says nothing about no-match behavior, exact vs fuzzy matching, or whether multiple competing definitions can be returned.

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?

Two compact sentences with the action front-loaded and the usage trigger last. The parenthetical example list is long but earns its place by pinning down an otherwise opaque domain vocabulary, though it makes the first sentence slightly heavy.

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?

For a one-parameter, read-only lookup with no output schema and no nested objects, the description covers what the tool does, what it returns, and when to call it. The remaining gap — behavior when the term is unknown or ambiguous — is minor at this complexity level.

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 0% for the single 'term' parameter, so the description must carry the meaning — and it does, stating the parameter takes exactly one LUMA term and supplying nine concrete examples that define the expected vocabulary. It does not say whether casing, abbreviations, or partial terms are accepted.

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?

Names a specific verb ('explain') and a well-defined resource ('one LUMA term'), and clarifies the output is definitions from the agent docs plus metric channels of the same name, which separates it from plain doc readers like read_doc. It stops short of explicitly naming the sibling it replaces for full-document lookups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use it when a user asks what something means' gives a clear triggering condition tied to the user's intent. There are no negative cases or named alternatives (e.g. use read_doc when the user wants the full document rather than a definition), so the agent must infer the boundary.

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