Skip to main content
Glama

search_shelf

Search the library by title, author, translator, blurb or group, also returning up to 20 matching section titles: Homer, Plato, Thucydides, Plutarch, Virgil, Livy and the rest of the Greek and Latin classics in the original beside English; the Pali Canon; Dostoevsky, Tolstoy, Pushkin in Russian; Camus, Kafka, Goethe; Philo, Josephus, the Mishnah in Hebrew and English, 1-3 Enoch, Jubilees, the Church Fathers, Aquinas, Calvin, Kierkegaard, Nietzsche... To find a passage inside a work, use read_work with find.

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

Input Schema

NameRequiredDescriptionDefault
groupNoOptional group filter, e.g. "Hidden books", "Rabbinic", "Church Fathers", "Commentaries"
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose a return trait (up to 20 matching section titles), which is genuinely useful, but says nothing about total result counts, pagination, ranking, case sensitivity, or whether matching is metadata-only versus full text.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the read_work routing sentence are well placed, but the middle of the description is a long marketing enumeration of authors and corpora (Homer through Nietzsche) that consumes most of the token budget without helping an agent decide or invoke correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter search tool with no output schema, the description conveys the resource and one aspect of the return value. It stops short of describing result ordering, limits beyond the 20 section titles, or behavior with an empty query, which leaves real gaps for invocation.

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 50%: group is documented in the schema, query is not. The description partly compensates by naming the fields query searches (title, author, translator, blurb, group), which tells an agent more than the bare schema, but it adds no format or matching-behavior detail.

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 opens with a specific verb and resource ("Search the library by title, author, translator, blurb or group") and adds the notable side effect of returning up to 20 matching section titles. It also separates itself from read_work for in-work passage lookup, though it does not differentiate itself from get_passage or list_editions.

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?

There is one explicit routing rule: "To find a passage inside a work, use read_work with find." That covers the passage case well, but the description never says when to prefer this over get_passage or list_editions, nor what happens when query is omitted and only group is supplied.

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