Skip to main content
Glama

LUMA NBA Impact Metrics

read_doc

Read-onlyIdempotent

Read one LUMA agent doc. ids: README, boundary, concepts, how-to-read-arc, metrics, validation, faq. boundary = house rules (read before quoting numbers); concepts = the models; metrics = every column; how-to-read-arc = what an ARC number means; validation = test results; faq.

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": {
      "id": "<id>"
    },
    "name": "read_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

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 only a light behavioral cue (read boundary before quoting numbers); it says nothing about document size, whether a call returns full text, or any failure modes, which matters since there is no output schema.

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?

One front-loaded sentence names the action, followed by a tightly compressed id-to-content map with zero filler. The semicolon-chain style is dense ("concepts = the models") but every clause carries information.

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 single-parameter, enum-constrained reader with no output schema, the description covers what an agent needs to pick the right document. The remaining gap is what a call actually returns (full text? truncated?) and the recommended reading order across docs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 full burden, and it does so by defining the meaning of every one of the seven enum values (README, boundary, concepts, how-to-read-arc, metrics, validation, faq). This is exactly the value-add the schema cannot supply.

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?

"Read one LUMA agent doc" is a specific verb+resource, and the enumerated id list makes the scope concrete. It does not explicitly position itself against similar siblings such as docs, explain, or start_here, so it stops short of the top mark.

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?

The per-id glosses implicitly tell the agent which doc answers which question, and "boundary = house rules (read before quoting numbers)" is an explicit usage cue. However, there is no statement of when to call read_doc at all versus the other documentation-oriented siblings, or of any prerequisites/ordering beyond that one hint.

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