ndl-search-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_bibliographyB | Find bibliographic records by title, author, or both. Start is one-based. |
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 1 tool
With only one tool, there is no possibility of confusion or misselection between tools. Any search request maps unambiguously to search_bibliography.
The single name follows a clear verb_noun snake_case pattern (search_bibliography), matching the convention implied by its description. No competing conventions exist to conflict.
A one-tool server is too thin for a bibliographic search service; only a single lookup operation is exposed. Reasonable scope would include at least record retrieval or listing tools.
The surface covers only search by title/author, with no way to fetch a full record by identifier, list available fields, or page results beyond a numeric Start. Agents hitting a record will have no follow-up operation to retrieve details.