library-enrichment
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| service_statusB | Inspect readiness and capabilities, without indexing. |
| resolve_libraryC | Establish exact identity and environment before research. |
| library_overviewB | Discover unfamiliar capabilities without knowing symbol names. |
| search_evidenceB | Search a bounded set of API, docs, examples, source, or release evidence. |
| inspect_symbolA | Read retained symbol evidence; explicit execution options can run isolated semantic or runtime inspection. |
| compare_releasesC | Discover additions/removals and non-API changes. |
| verify_usageA | Test a proposed invocation or composition in isolation. |
| read_artifactA | Retrieve large result sections without flooding context. |
| job_controlA | Observe or cancel an explicitly submitted long-running operation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| research_workflow | Current selection, coverage, jobs, recovery and result-reading guidance. |
TDQS
Scored across 9 tools
Each tool maps to a distinct phase in the research workflow: status, identity, overview, evidence search, symbol inspection, release comparison, usage verification, artifact retrieval, and job control. Even the two preflight tools are clearly separated by readiness vs. identity.
The majority use verb_noun (search_evidence, inspect_symbol, compare_releases, verify_usage, read_artifact), but service_status, library_overview, and job_control are noun_noun, creating an inconsistent pattern. Names remain readable, so not chaotic.
Nine tools is a well-scoped count for a specialized library-research server; each tool covers a distinct step without redundancy or bloat.
The set covers the full discovery, inspection, comparison, verification, and retrieval lifecycle, with job control for long operations. The only minor gap is the absence of an explicit write-back/enrichment-submission tool, though the server appears read-oriented by design.