Skip to main content
Glama
smeet666

mcp-archiveorg

Search works and editions

search_books
Read-onlyIdempotent

Search Internet Archive's Open Library by title, author, subject, place, period, or person; sort by reader rating or count to choose what to read.

Instructions

Find a book on Open Library, the Internet Archive's catalogue of works, either by name or by description. Pass 'query' when you know what you are looking for: a title, an author. Pass the criteria instead when you do not, and they combine: 'subject' for what a work is catalogued under, 'place' for where it is set, 'time' for the period it treats, 'person' for who it is about, plus ranges on the year of first publication and on the page count. 'sort' by rating or by readers answers 'what is worth reading', which relevance alone does not. Answers who wrote a book, when it first appeared and how many editions exist, which the item catalogue describes poorly because it holds one upload at a time. 'archive_identifiers' lists scans of the work: pass one to get_item, or use it to read the book itself. Use this to identify a work, and search_inside to find a phrase within one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sortNo'rating' is how readers scored it, 'readers' is how many recorded reading it, and both answer a question relevance cannot.relevance
timeNoThe period the work treats, such as '20th century'.
limitNo
placeNoWhere the work is set, such as 'Shanghai'.
queryNoTitle or author, as free text. Optional when a criterion below is given.
personNoWho the work is about, such as 'Napoleon'.
subjectNoWhat the work is catalogued under, such as 'grief' or 'spy stories'. Also carries prizes and lists, such as 'Booker Prize'.
year_toNoLatest first publication.
languageNoThree-letter code of the language, such as 'eng' or 'fre'.
pages_maxNoLongest acceptable work. The count is a median across editions.
pages_minNoShortest acceptable work.
year_fromNoEarliest first publication.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
booksYes
notesYes
queryYesWhat was searched for, criteria included.
totalYesWorks matching, not the number returned.
Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world hints. The description adds context about what results include (author, first publication year, edition count) and why the item catalogue is inadequate. However, it references 'archive_identifiers' without clarifying whether it's an input or output field, which introduces slight ambiguity.

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 description is relatively long but front-loaded with the core purpose. Every sentence contributes value, explaining usage, output, and relationships. However, the 'archive_identifiers' reference is tangential and could be condensed or clarified to avoid confusion.

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?

For a tool with 13 optional parameters and an output schema, the description covers the key decision points (query vs. criteria, sort semantics) and relationships to sibling tools. It could be more explicit about combining all criteria or pagination, but the schema covers those details, and the description provides sufficient context for an agent to use the tool effectively.

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 covers 85% of parameter descriptions. The description adds semantic guidance on when to use query vs. criteria, and how sort options answer 'what is worth reading.' This goes beyond the schema's per-field descriptions. The mention of 'archive_identifiers' could confuse the agent about a non-existent input parameter.

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?

The description clearly states the tool 'Finds a book on Open Library' with a specific verb and resource. It distinguishes itself from siblings by explaining its role in identifying works and directing users to search_inside for phrases and get_item for scans.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly explains when to use this tool: 'Use this to identify a work, and search_inside to find a phrase within one.' It also provides guidance on choosing between query and criteria parameters, and when to use sort options. Alternatives are clearly named.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smeet666/mcp-archiveorg'

If you have feedback or need assistance with the MCP directory API, please join our Discord server