Skip to main content
Glama
malkreide

eth-library-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

eth_get_resource

Read-onlyIdempotent

Retrieve a specific resource from ETH Library using its MMS-ID. Get details and availability status, with clear error handling for invalid IDs.

Instructions

Ruft eine einzelne Ressource der ETH-Bibliothek anhand ihrer MMS-ID ab.

FID-003: Kennt die Quelle die MMS-ID nicht, kommt ein leeres Ergebnis mit hint — keine geratenen Angaben zu einem Datensatz, der nicht geliefert wurde. Ein Fehlschlag (401, 404, Zeitüberschreitung) kommt dagegen als isError und ist keine Aussage über den Bestand.

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_get_resourceOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.3.3

TDQS

A4.4/5.0
Behavior5/5

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

The description explains important non-obvious behavior: an unknown MMS-ID yields an empty result with a `hint` rather than fabricated data, while HTTP failures such as 401, 404, or timeout surface as `isError` and do not indicate holdings. This goes beyond the readOnly/openWorld/idempotent annotations by clarifying result semantics.

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 short, front-loaded with the main action, and the second part adds essential edge-case semantics without repetition. Every sentence earns its place.

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 simple get-by-ID tool, the description covers the most important call-specific behaviors (unknown ID vs. error handling). It does not describe the shape of a successful response, but given no output schema, the natural resource-return semantics and the provided error/hint distinction are sufficient for an agent to invoke it correctly.

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 adds value around the `mmsid` parameter's unknown-ID behavior, but it does not explain `lang` or `include_availability`. The schema already provides descriptions for those parameters, so the description's contribution beyond the schema is limited rather than compensating for a coverage gap.

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 ('Ruft ... ab') and a specific resource ('eine einzelne Ressource der ETH-Bibliothek') keyed on MMS-ID, which clearly distinguishes it from the sibling search tools. The intent to retrieve one resource by ID is unambiguous.

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 description makes clear this is for fetching a single resource by known MMS-ID, which gives the agent a clear context for using it. It does not explicitly name alternatives or exclusion conditions, but the ID-based retrieval semantics imply the appropriate use case relative to the search siblings.

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