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

norway-archives-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nb_download_page

Idempotent

Download one page image from the currently open National Library item as a new .jpg file by specifying item ID plus page, page ID, or image number; existing files are not overwritten.

Instructions

Download one page image of a National Library item that is open where you are.

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>",
      "item_id": "<item_id>"
    },
    "name": "nb_download_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoThe printed page number.
imageNoInstead: the image number, 1-based.
item_idYesThe item id from nb_search.
page_idNoInstead: the page 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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the write-and-idempotent profile is covered structurally. The description adds only that the page belongs to a currently open item; it says nothing extra about where the file lands, failure modes, or whether re-running the same request is safe — details that live in the schema, not the description.

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?

A single front-loaded sentence with no filler. Minor deduction for the vague trailing clause 'where you are,' which reads imprecisely compared with the rest of the phrasing.

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

Completeness3/5

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

For a 6-parameter download tool with no output schema, the description covers the what and the state prerequisite but omits what the call returns or confirms and any note on failure when the item is not open. With schema descriptions carrying parameter detail, this is adequate but not complete.

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 itself explains page vs. image vs. page_id, max_pixels, and the destination file constraint. The description adds no meaning beyond that baseline, which is acceptable here but not differentiating.

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 specific verb and resource: 'Download one page image of a National Library item,' which separates it from the da_* archive siblings by naming the National Library corpus. It stops short of explicitly naming the closest alternative (nb_get_page) for fetching page data without downloading an image.

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?

'that is open where you are' implies a prerequisite (the item must already be open/loaded, presumably via nb_search), which is useful but phrased loosely. There is no explicit when-not or naming of nb_get_page as the alternative for non-download access.

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