nerve-lit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PDF_DIR | Yes | Directory where PDFs are stored | |
| NCBI_EMAIL | Yes | Your email address (required by NCBI) | |
| NCBI_API_KEY | No | Optional API key for higher rate limits | |
| UNPAYWALL_EMAIL | Yes | Your email address (required by Unpaywall) |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_nerve_litA | Doorzoek de peripheral-nerve-surgery literatuurdatabank semantisch. |
| get_nerve_lit_articleB | Haal de volledige metadata van één artikel op via zijn PMID. |
| get_nerve_lit_statsC | Toon de omvang en toestand van de literatuurdatabank. |
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 3 tools
The three tools map to clearly distinct operations: semantic passage search, single-article metadata retrieval by PMID, and database statistics. An agent can trivially choose between searching, fetching a known article, and inspecting corpus coverage, since the inputs (free-text query vs. PMID) also differ.
All three names use the same snake_case verb_noun pattern with a shared 'nerve_lit' domain token (search_/get_/get_). The convention is predictable and unambiguous.
Three tools is on the lean side but fits a narrowly scoped, read-only literature search service where each tool earns its place. No filler or redundant tools are present.
The surface covers the core lifecycle of a literature database: discover passages, retrieve full metadata, and check corpus status, with useful filters (year range, full-text only). Minor gaps remain, such as lookup or export by DOI and batch/citation retrieval, but these are workarounds rather than blockers.