Skip to main content
Glama
Sign In
Open Library MCP Server

Open Library MCP Server

by jay1234624
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

read_book_snippet

Search inside books for specific text and retrieve relevant snippets. Find passages matching your query across available books.

Instructions

Search inside books and return text snippets when available

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": {
      "query": "<query>"
    },
    "name": "read_book_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of snippets to return (default 3, max 10)
queryYesText to search for inside books, e.g. 'ring of power'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description must carry full burden. Only hints 'when available' about snippet availability. Does not disclose error handling, authentication needs, or behavior when no results are found.

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?

Single concise sentence that conveys the core purpose. Could be improved by structuring into two sentences, but no wasted words.

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

Completeness2/5

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

With no output schema and no annotations, description is too minimal. Does not specify snippet format (e.g., page numbers, context), conditions for unavailability, or expected output structure.

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% with descriptions for both parameters. Description adds no extra meaning beyond schema; baseline of 3 is appropriate.

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?

Description clearly states verb 'search', resource 'books', and result 'text snippets'. It distinguishes from siblings like search_books (metadata search) and get_book_summary (summary).

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?

Implied usage for searching inside books, but no explicit guidance on when to use vs. alternatives like search_books or get_book_details_by_isbn. No when-not-to-use or prerequisites mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools