Skip to main content
Glama
Sign In
german-archives-mcp

german-archives-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hessen_image

Idempotent

Download one page image of a Hessian register from Arcinsys Hessen and save it as a new JPG so you can read and cite it.

Instructions

Download one page image of a Hessian register from Arcinsys Hessen, so it can be read.

Read the page before citing it. page is the image's place in the viewer, not the number written on the page; pages still under a protection period are left out by the archive. Saves a new .jpg or .jpeg file, never returned inline: not hidden, not under ~/Library, and inside the operator's download folder when one is set. Cite by the citation returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item": "<item>",
      "destination": "<destination>"
    },
    "name": "hessen_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesA signature from hessen_search, e.g. 'HStAM 922 Nr. 6013', or the unit's Arcinsys address.
pageNoWhich image, 1-based, in the order of Arcinsys's viewer.
destinationYesAbsolute path of a new .jpg file, e.g. '/path/to/images/922-6013-bild-2.jpg'. The directory must exist and the file must not: nothing is overwritten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that a new .jpg is written and never overwritten, that content is never returned inline, the exact placement rules (not hidden, not under ~/Library, inside the operator's download folder when set), and that pages under a protection period are silently omitted. That omission detail materially affects what an agent will receive.

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

Conciseness4/5

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

Purpose is front-loaded in the first sentence and the remaining lines are dense with operational constraints rather than filler. The file-placement clause is slightly cryptic but each sentence carries information.

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 3-parameter tool with full schema coverage and no output schema, the description covers the main unknowns: file creation semantics, no-overwrite behavior, and where to get the citation. Minor gaps remain around image format/resolution and what happens if the requested page falls inside a protection period.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: `page` indexes the viewer order rather than the printed page number, and the protection-period omission means index positions do not map cleanly to physical pages. It also points at the `citation` value for citing.

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?

States a concrete verb and resource ('Download one page image of a Hessian register from Arcinsys Hessen') plus the intent ('so it can be read'). The Hessian/Arcinsys scoping implicitly separates it from the labw/nrw/rlp image siblings, though it never names an alternative explicitly.

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?

'Read the page before citing it' gives a workflow rule, and the `item` parameter ties the call to a prior hessen_search result, so the sequencing is clear. It stops short of stating exclusions or naming sibling tools for other regions.

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