Skip to main content
Glama

Tribute Paper

Get a reading

get_reading
Read-onlyIdempotent

The full words of one reading from Tribute Paper's library, by slug (from find_readings), with its author or reference, the line to print under it in a program, when it is often read, how long it takes to read aloud, where the words come from and why it is free to print. Quote the words exactly as given.

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": {
      "slug": "<slug>"
    },
    "name": "get_reading"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe reading's slug, e.g. psalm-23.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description still adds real value by enumerating the returned metadata (author/reference, program line, occasion, read-aloud duration, provenance, free-to-print rationale) and by stating the fidelity expectation 'Quote the words exactly as given.' Missing is any note on behavior for a slug that does not exist.

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 core purpose and key parameter are front-loaded in the opening clause, and the long enumeration of returned fields is dense but each item describes something an agent would want to know. The trailing fidelity instruction lands well at the end, though the single run-on sentence is slightly heavy.

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 return-value burden and does so by listing the metadata fields alongside the words themselves. Combined with full annotation coverage and a fully documented single parameter, the definition is nearly complete; only error handling for an unknown slug is left implicit.

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 coverage is 100%, so the schema already documents the single slug parameter with its pattern and an example. The description's only addition is the provenance hint that the slug comes from find_readings, which is useful but minor, keeping this at the high-coverage baseline.

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 states precisely what is retrieved: the full words of a single reading from Tribute Paper's library, keyed by slug. It is clearly distinct from the sibling find_readings, which it names as the slug source. The only weakness is that the verb is implicit in the noun phrase rather than stated outright.

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 parenthetical '(from find_readings)' gives a concrete workflow prerequisite: obtain the slug from the search tool first. However, there is no explicit statement of when to prefer this over find_readings or other siblings, and no when-not guidance or exclusion for invalid slugs.

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