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

norway-archives-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

da_download_page

Idempotent

Downloads one scanned Digitalarkivet page to a new JPG and returns its citation details, including source, archive reference, image number, and permanent link.

Instructions

Download one scanned page from Digitalarkivet so it can be read.

This is the step that turns a hit into evidence. Returns the citation (source, archive reference, image number, permanent link). Census pages (ft… ids) come at full resolution only.

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": {
      "destination": "<destination>"
    },
    "name": "da_download_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageNo…and the image number, 1-based.
page_idNoPermanent page id, e.g. 'kb20070419660152' or 'ft2009…'.
source_idNoInstead: the source id…
max_pixelsNoLongest side in pixels; 0 for full resolution.
destinationYesAbsolute path of a new .jpg file. 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

A3.7/5.0
Behavior4/5

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

Annotations already declare the write/idempotent/non-destructive profile, so the description is not obligated to repeat it. It does add real behavioral context beyond that: the return payload (citation with source, archive reference, image number, permanent link) and the resolution quirk that census pages (ft… ids) only come at full resolution. It omits saying that the downloaded file is never overwritten, though the schema covers that.

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?

Three short sentences, front-loaded with the core action and followed by the value proposition and one special-case caveat. No padding, though 'so it can be read' is slightly redundant with 'turns a hit into evidence'.

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?

With no output schema, the description usefully describes what comes back (citation fields), and it flags the main behavioral edge case (census pages at full resolution). The only gap is guidance on choosing between da_download_page and da_get_record/da_get_source for retrieving evidence, which would fully close the picture for a 5-parameter 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?

Schema description coverage is 100%, so the schema already explains page_id, image, source_id, max_pixels and destination in detail. The description adds only a light hint that 'ft…' page ids correspond to census pages and carry a resolution constraint. That is marginal added meaning, so the baseline 3 applies.

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 specific verb and resource — 'Download one scanned page from Digitalarkivet' — making the scope (single page, one archive) unambiguous. Naming Digitalarkivet implicitly separates it from the nb_* siblings, but it never states that distinction explicitly, so it falls short of a 5.

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

Usage Guidelines3/5

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

'This is the step that turns a hit into evidence' implies the tool is used after a search returns a hit, which is useful sequencing context. There is no explicit when-not guidance, no mention of when to pick da_get_record or da_get_source instead, and no note on prerequisites (e.g., needing a page_id from da_list_pages).

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