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

norway-archives-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nb_get_page

Read-only

Retrieve one page of a National Library item to get its available OCR text and citation, using an item ID with a page number, image number, or page ID.

Instructions

Read one page of a National Library item: its OCR text where it is open, and its citation.

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

Input Schema

NameRequiredDescriptionDefault
pageNoThe printed page number, as a snippet gives it.
imageNoInstead: the image number, 1-based.
item_idYesThe item id from nb_search.
page_idNoInstead: the page id from nb_search_inside.
include_textNoReturn the page's OCR text when open.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one real behavioral nuance — text is returned only 'where it is open' — but is silent on what happens for a closed/restricted page (error, empty text, citation only), which is the main behavioral question an agent would have.

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 compact sentence with the resource and return contents front-loaded and no filler. The phrasing around 'where it is open' is slightly terse, but nothing is wasted.

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 names what comes back (OCR text plus citation), which is the essential return information for this tool. Combined with 100% schema coverage and read-only annotations, this is nearly complete; only the closed-item behavior is unstated.

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 all five parameters including the page/page_id/image alternatives are already documented in the schema. The description adds no additional meaning about these selectors, which is acceptable given the schema does the work but leaves no value add.

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 uses a specific verb ('Read') and a bounded resource ('one page of a National Library item'), and states the two things returned: OCR text and citation. It is clearly not a search or download tool, though it does not explicitly name nb_download_page as the contrasting sibling.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternative is named. Nothing tells the agent when to prefer this over nb_download_page or when to first call nb_search_inside to obtain a page_id; that routing knowledge exists only implicitly in the schema.

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