Skip to main content
Glama

LUMA NBA Impact Metrics

docs

Read-onlyIdempotent

Map of the LUMA agent docs (agent-to-agent): house rules, what each model is, every column defined, how to read ARC, published test results, FAQ, and the public pages to read for more. Read once per session, before explaining any LUMA model to a user.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 a closed world, so the safety profile is covered. The description adds a genuinely useful behavioral note (read once per session, i.e., it is a session-level orientation artifact), but says nothing about the size or shape of what it returns.

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?

One dense sentence with the contents list first and the usage instruction last. Every enumerable item is concrete and none of the wording is filler.

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 zero-parameter, read-only orientation tool, the agent learns what it contains and when to call it. The only gap is not pointing to read_doc/read_page for following up on an individual page, which the phrase 'public pages to read for more' only hints at.

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?

Zero parameters at 100% schema coverage, so there is no parameter semantics to explain; baseline 4 applies.

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?

States a specific resource (the LUMA agent docs) and enumerates its scope: house rules, model definitions, column definitions, ARC reading, test results, FAQ, and further public pages. It is clearly distinct from read_doc/read_page as an orientation map rather than a document fetcher, though it never names those siblings.

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?

Gives an explicit trigger: 'Read once per session, before explaining any LUMA model to a user.' That is clear when-to-use guidance, but it does not state when to skip it in favor of read_doc/read_page for a specific page.

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