Skip to main content
Glama

LUMA NBA Impact Metrics

sql

Read-onlyIdempotent

Read-only SQL (DuckDB dialect) over the warehouse views: players, player_seasons (listed position / height by season), games, box_game, box_season, arc_season, arc_live, loki, loki_release, pac_season, skills_season (19 skill groups + season percentiles), onoff_season and lineups (incl. four factors and rebound shares), wowy, channels, xpts_rapm. One SELECT only, max 200 rows; PIVOT is not allowed (use max(x) filter (where ...)); quote "window" and "asof"; write every column alias with AS (a bare alias like load / value / rows / minutes is a syntax error). Use other tools first; call describe for column meanings.

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": {
      "query": "<query>"
    },
    "name": "sql"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: hard row cap, single-statement restriction, dialect-specific syntax traps (PIVOT, reserved words, bare aliases), and the expectation that this is a fallback after other tools. These are operational constraints an agent could not infer from the annotations.

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?

Front-loaded with purpose, then constraints, then routing advice — a sensible order. The long enumeration of view names is dense but each name earns its place as a discoverability aid; the parenthetical annotations (skill groups, four factors) are borderline but still informative.

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 free-form SQL tool with no output schema, the description covers the critical failure modes (statement count, row cap, dialect quirks) and defers column semantics to describe. The only real omission is the undocumented `limit` parameter and any note on how results/errors are returned.

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 well for the query parameter — one SELECT only, 200-row cap, PIVOT ban, quoting of "window"/"asof", mandatory AS aliases — but never explains the optional `limit` parameter or how it interacts with the 200-row ceiling.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Read-only SQL (DuckDB dialect) over the warehouse views') and then enumerates the exact views available, so an agent knows precisely what this tool queries and how it differs from structured siblings like leaderboard, lineups, or wowy.

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

Usage Guidelines5/5

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

It gives explicit routing guidance: 'Use other tools first; call describe for column meanings.' That names both the preferred alternatives and the specific sibling to consult for schema knowledge, which is exactly the when-to-use/when-not-to-use information an agent needs.

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