Skip to main content
Glama
sandraschi

digibib

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

digibib

Read Digitale Bibliothek 5 CD-ROM volumes by listing installed volumes, browsing tables of contents, extracting decoded chapter or record text, searching full text, and retrieving figure images.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
rootNoOverride the install root (default DIGIBIB_ROOT or K:\...).
levelNoimages: zoom level (default: highest).
limitNosearch: max hits (default 20, max 100).
queryNosearch: FTS5 query (words, AND/OR/NOT, "phrase", prefix*).
max_depthNotoc: limit nesting depth.
operationNolist_volumes | descriptor | toc | node_text | record_text | search | imageslist_volumes
volume_idNoVolume folder id, e.g. 'DB008' (all ops except list_volumes).
node_indexNotoc node index (node_text).
record_indexNorecord index (record_text).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it discloses important behavior: the first search per volume builds an FTS cache (~10 s), images are served via a REST endpoint, and text decoding is v2 but not byte-faithful. It stops short of permissions or error behavior, but the disclosed traits are substantial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and then organized as a compact operation list. Every bullet adds information needed to select an operation or set a parameter, and the closing note about decode fidelity is relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given seven operations and nine optional parameters, the description explains operation roles, parameter applicability, and workflow-adjacent details such as how toc exposes node indexes used by node_text. An output schema exists, so return-value explanation is not required, and the description is complete enough to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents parameters at a baseline level. The description adds operation-specific meaning: which parameters apply to toc, node_text, record_text, search, images, and volume_id. This is useful beyond the schema, though not exhaustive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'read Digitale Bibliothek 5 volumes.' It then enumerates all seven operations with concrete outputs, so an agent understands the tool's scope without consulting another tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is clear for each operation: search requires query, images uses level or defaults to the highest, and volume_id applies to all operations except list_volumes. It does not explicitly say when to avoid the tool, but no alternatives exist and the operation-level guidance is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools