Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DIGIBIB_ROOTNoThe install root scanned for Digitale Bibliothek CD-ROM volumes. Defaults to K:\Digitale Bibliothek\Bibliothek.K:\Digitale Bibliothek\Bibliothek

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": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
digibibA

DIGIBIB - read Digitale Bibliothek 5 volumes.

Operations:

  • list_volumes -> every installed CD-ROM volume: {id, title}.

  • descriptor -> the volume's DIGIBIB.TXT identity keys.

  • toc -> the table of contents as a nested tree (node index + record index per node). Use max_depth to trim.

  • node_text -> decoded text for a TOC node: the full chapter extent (record..record_end, records_total, truncated flag).

  • record_text -> decoded text for a raw TEXT.DKI record index.

  • search -> full-text search over decoded text (needs query): [{record, node_index, chapter, snippet}]. First search per volume builds an FTS cache (~10 s), then instant.

  • images -> figures at a zoom level (needs level or takes the highest): {levels, level, images: [{name, width, height, bpp, bytes, url}]}. Binary via the REST image endpoint (see url per figure).

NOTE: text decode is v2 (flowing paragraphs, heads dropped); output is readable but not yet byte-faithful.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 1 tool

Disambiguation4/5

The single dispatcher tool exposes clearly separated operations (list_volumes, descriptor, toc, node_text, record_text, search, images) with distinct inputs and outputs. The only real overlap is node_text vs record_text, which both return decoded text and differ only by addressing scheme (TOC node vs raw TEXT.DKI record index) — the descriptions clarify this, but an agent could still pick the wrong one.

Naming Consistency4/5

The operations inside the tool consistently follow a snake_case verb_noun pattern (list_volumes, node_text, record_text). The tool itself is a single server-named dispatcher ('digibib') rather than a verb_noun action, which is a minor deviation but acceptable for a multi-operation facade.

Tool Count3/5

A single exposed tool would normally feel thin, but it packs seven substantive operations covering the whole read lifecycle, so the surface is larger than the count suggests. Still, the single-tool dispatch pattern makes discovery and selection harder than a small set of explicit tools would.

Completeness4/5

For a read-only CD-ROM library reader the coverage is strong: volume listing, metadata, TOC navigation, chapter/record extraction, full-text search, and figure retrieval. Gaps are minor — no cross-volume aggregated search and no export/citation output, but agents can work around both by iterating volumes.

Maintenance

ActivityMaintained
ResponsivenessNo issues