Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PDF_DIRYesDirectory where PDFs are stored
NCBI_EMAILYesYour email address (required by NCBI)
NCBI_API_KEYNoOptional API key for higher rate limits
UNPAYWALL_EMAILYesYour 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_nerve_litA

Doorzoek de peripheral-nerve-surgery literatuurdatabank semantisch.

Args:
    query: de vraag in natuurlijke taal, bv. "supercharged end-to-side AIN naar ulnaris".
    k: aantal passages om terug te geven (default 8).
    year_from: enkel artikels vanaf dit publicatiejaar.
    year_to: enkel artikels tot en met dit publicatiejaar.
    full_text_only: alleen passages uit volledige artikels, niet uit abstracts.

Returns:
    De relevantste passages met hun citaat (titel, tijdschrift, jaar, PMID, DOI).
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues