Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LIBRARY_PATHNoThe path to the Directmedia 'Digitale Bibliothek' collection directory

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
list_volumesA

List all available Directmedia volumes/bände

Returns a list of all volumes in the Digitale Bibliothek collection with metadata about each volume.

get_volume_infoB

Get detailed information about a specific volume

search_textC

Search for text across volumes

get_text_contentC

Extract text content from a volume

get_navigation_treeB

Get the navigation tree/structure for a volume

analyze_volume_structureC

Analyze the file structure and format of a volume

set_library_pathB

Set the path to the Digitale Bibliothek collection

convert_volume_to_epub_fileB

Convert a Directmedia volume to EPUB format for e-book readers

batch_convert_to_epubC

Convert multiple Directmedia volumes to EPUB format

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 9 tools

Disambiguation4/5

Most tools are clearly distinct: list_volumes enumerates all volumes while get_volume_info targets a single one; search_text finds passages and get_text_content extracts full content. The only minor overlap is between get_navigation_tree and analyze_volume_structure, but descriptions indicate different kinds of structure (user-facing navigation vs. technical file format).

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern, e.g., list_volumes, get_volume_info, search_text, get_navigation_tree. The batch conversion tool (batch_convert_to_epub) is a minor variation but still fits the overall convention. No mixed casing or unpredictable verb usage.

Tool Count5/5

Nine tools is well within the ideal range for a domain-specific server. Each tool maps to a clear need: discovery, metadata, search, text retrieval, structure, configuration, and conversion. The set is compact but not sparse, with no redundant tools.

Completeness5/5

The set covers the full workflow for a digital library server: list and inspect volumes, search and read content, navigate structure, set the library path, and convert to EPUB including batch conversion. Since the domain is a read-only archive, CRUD operations like update/delete are not missing—they are out of scope.

Maintenance

ActivityActive
ResponsivenessNo issues