Skip to main content
Glama
malkreide

eth-library-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

eth_search_archive

Read-onlyIdempotent

Search a specific ETH Library archive to locate its contents; select the collection (e.g., Max Frisch, Thomas Mann, Bildarchiv) and apply an optional query to narrow results.

Instructions

Durchsucht ein spezifisches Archiv oder eine Sammlung der ETH-Bibliothek.

FID-003: Ein leeres Ergebnis nennt im Feld hint den nächsten Versuch — das Archiv ist ein Filter, und der Bestand ausserhalb davon ist damit nicht geprüft. Keine geratene Angabe an die Stelle eines fehlenden Treffers setzen.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "eth_search_archiveOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.3.3

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses meaningful behavioral details: the `hint` field on empty results, the fact that the archive acts as a filter so outside holdings are not checked, and the instruction not to substitute guessed data for missing results. This materially helps an agent interpret search results correctly.

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 compact and front-loaded: the core action appears in the first sentence, and the FID-003 guidance is a separate, dense, non-redundant block. Every sentence earns its place with no filler.

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

Completeness4/5

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

For a read-only archive search tool, the description covers scope, usage, and the important empty-result behavior, which is the main non-obvious case. It does not describe the successful response payload beyond the `hint` field, but given the strong annotations and detailed input schema, the description is sufficiently complete for selecting and invoking the tool.

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

Parameters3/5

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

The description itself adds no parameter-level detail, and context reports low schema description coverage. However, the visible input schema thoroughly documents the required `archive` enum and its meanings, plus `query`, `limit`, and `offset`, so an agent can still invoke the tool correctly. The description does not compensate for the reported coverage gap, but the schema carries the burden.

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

Purpose4/5

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

The description opens with a concrete verb ('Durchsucht') and a clear resource ('ein spezifisches Archiv oder eine Sammlung der ETH-Bibliothek'), so an agent can tell this is scoped to one archive or collection. It does not explicitly differentiate itself from siblings such as eth_search_resources or eth_search_by_type, which keeps it from the top score.

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?

The first sentence makes the usage context clear: search within a specific archive or collection. The FID-003 note adds an important operational rule about empty results and not guessing when the archive filter returns no matches, though it does not name alternative tools or give an explicit when-not-to-use statement.

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