Skip to main content
Glama

LUMA NBA Impact Metrics

read_page

Read-onlyIdempotent

Read a public LUMA page as text (lumahoops.org), for when the agent docs point to a page: e.g. /luma/arc/about, /luma/loki/about, /luma/pac, /luma/rapm, /luma/wins, /luma/changelog, /luma/papers/pac-working-paper-v1.pdf, /luma/research/possession-by-possession-fundamentalism. Long pages come in chunks: pass offset to continue.

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": {
      "url": "<url>"
    },
    "name": "read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeslumahoops.org URL or path
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds real value beyond that by disclosing the return format (plain text) and the chunking/pagination behavior with the `offset` continuation cue.

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?

The purpose and the use condition are front-loaded in the first clause, with pagination advice at the end. The long enumeration of seven example paths is slightly over-long but each example illustrates a different page family, so it earns most of its space.

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?

With no output schema, the description carries the burden of explaining the return value, which it does (text, chunked). For a two-parameter read tool with strong annotations this is nearly complete; only the sibling-selection question and termination of the offset loop are unaddressed.

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 only 50% (the `offset` property is undocumented in the schema), and the description compensates by explaining that long pages arrive in chunks and that `offset` continues to the next chunk. The `url` parameter is well covered by both the schema and the example paths, so the gap is closed.

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?

The description gives a specific verb and resource ("Read a public LUMA page as text") plus the host it targets, so an agent knows exactly what the tool fetches. It does not distinguish itself from the sibling tools `docs` and `read_doc`, which also sound like reading operations, so a 5 is not warranted.

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?

"For when the agent docs point to a page" gives a clear triggering condition, and the sample paths show the shape of valid targets. There is no guidance on when not to use it or which sibling to pick instead (e.g. `read_doc` vs this), which keeps it below 5.

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