MCP Open Library & File Search Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_authorC | Search for books on the Open Library API by author name. |
| search_in_fileB | Search for a specified keyword within a given file. Returns the lines containing the keyword and their line numbers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have entirely different purposes—one searches Open Library by author name, the other searches within a local file. No overlap or ambiguity is possible.
Both tools use the 'search_' prefix followed by a specifier (author vs. in_file), showing a consistent verb-first pattern. Minor variation in specifier type (noun vs. prepositional phrase) is acceptable.
With only two tools covering two distinct domains (Open Library and file search), the server feels thin and unfocused. Each domain would benefit from additional tools to be useful, making the count too low for the stated scope.
The server provides only one operation per domain: author search and in-file keyword search. Missing are common complementary tools like book search by title/ISBN, file listing, or multiple search modalities. The tool surface is severely incomplete for both purposes.