Skip to main content
Glama

Tribute Paper

Find readings

find_readings
Read-onlyIdempotent

Searches Tribute Paper's library of 95 funeral and memorial readings: scripture (World English Bible), poems, hymns, prayers and short verses, all free to print in the US, UK, Canada and Australia. Search by words (a title, author, line or theme), by kind, by faith, or by occasion (for a mother, a father, a child, a spouse, a sudden loss, a long life, a celebration of life, the graveside, a veteran). Returns titles, authors, opening lines and reading-aloud time; get_reading gives the full words.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly this kind: scripture, poem, hymn, prayer, short-verse.
faithNoOnly readings used in this tradition: christian, catholic, jewish, non-religious.
limitNoHow many results to return (1 to 20, default 8).
queryNoWords to look for, e.g. "psalm 23", "rossetti", "do not stand at my grave", "garden".
occasionNoOnly readings often chosen for: mother (for a mother), father (for a father), child (for a child), spouse (for a husband or wife), sudden-loss (sudden loss), long-life (a long life), celebration-of-life (celebration of life), graveside (at the graveside), veteran (for a veteran).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds real value by disclosing the licensing constraint ("free to print in the US, UK, Canada and Australia") and the return shape (titles, authors, opening lines, reading-aloud time). It omits ranking/relevance behavior and whether search terms combine with AND or OR.

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 scope and library size are front-loaded, and the closing sentence about get_reading is well placed. The middle sentence is long and carries a heavy parenthetical occasion list, but every element maps to an actual parameter or return field, so little is wasted.

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 five-parameter, all-optional read-only search with no output schema, the description covers the domain, the filter dimensions, the return fields, and the full-text alternative. Nothing essential to selecting or invoking the tool is missing.

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 100%, so the baseline is 3; the description goes slightly beyond by clarifying that the query matches a title, author, line, or theme (not just literal strings) and by restating the occasion values in human phrasing such as "for a mother" and "the graveside." The added meaning is modest but genuine.

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?

States a specific verb and resource ("Searches Tribute Paper's library of 95 funeral and memorial readings") and enumerates the content types it covers. It also distinguishes itself from the sibling get_reading by noting that get_reading returns the full words, so an agent can route correctly without opening a schema.

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 clear usage contexts — search by words, kind, faith, or occasion — and names the alternative (get_reading) for retrieving full text. It does not state explicit when-not conditions or explain how results are ranked, so the guidance is strong but not exhaustive.

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