Skip to main content
Glama

LUMA NBA Impact Metrics

start_here

Read-onlyIdempotent

CALL THIS FIRST. Returns the LUMA guide (LUMA.md): every table and column, conventions (seasons, heights, positions, per-100, traded players), worked SQL recipes, what is NOT available, and the rules for crediting the data. Read it before writing sql.

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": "start_here"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context by specifying what the returned guide covers, including worked SQL recipes, unavailable data, and crediting rules, though it does not describe the exact output format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is two sentences, front-loaded with the critical instruction 'CALL THIS FIRST.' Every clause adds useful detail about the guide's contents or the required reading order, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter onboarding tool with no output schema, the description is complete enough. It states what is returned, why it matters, when to call it, and what the guide covers, so an agent can invoke it correctly without further context.

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?

The tool has zero parameters, so there are no parameter semantics to clarify beyond the baseline. The description correctly does not waste space discussing inputs, and the schema coverage is complete for an empty object.

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 uses a specific verb and resource: 'Returns the LUMA guide (LUMA.md)'. It then enumerates the guide's contents (tables, columns, conventions, SQL recipes, unavailable data, crediting rules), making the tool's purpose unmistakable and distinguishing it as the onboarding step before using the 'sql' sibling.

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?

The description gives explicit ordering guidance with 'CALL THIS FIRST' and 'Read it before writing sql.' That tells the agent exactly when to use this tool relative to the query-writing workflow, leaving little room for mis-selection.

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