LCSH MCP 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_lcshC | Search Library of Congress Subject Headings (LCSH) using the public suggest2 API. Returns a dictionary with the top results. |
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 ambiguity or overlap between tools. The single tool 'search_lcsh' has a clearly defined and distinct purpose.
The naming follows a consistent verb_noun pattern with 'search_lcsh'. With only one tool, there is no inconsistency to evaluate, and the pattern is clear and appropriate.
A single tool is too few for a server focused on LCSH, as it lacks basic operations like browsing, filtering, or retrieving detailed subject information. This minimal set limits functionality and agent workflows.
The server is severely incomplete for LCSH operations; it only offers search without supporting actions like get_subject_details, list_subjects_by_category, or related term lookups. This creates significant gaps for agent tasks.