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

norway-archives-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

da_get_record

Read-only

Retrieve one transcribed Norwegian archive record with its fields, every named person, and permanent scanned-page IDs for downloading the source image.

Instructions

Read one transcribed record: its fields, everyone named in it, and its scanned page.

scanned_pages gives the permanent page id to pass to da_download_page.

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": {
      "record": "<record>"
    },
    "name": "da_get_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordYesA record address from da_search_persons, or its path, e.g. 'view/255/pd00000024592808' or 'census/person/pf01038322000172'.
refreshNoTrue asks again instead of using the cached answer, and replaces it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/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 genuinely useful behavioral detail by describing the shape of the result (fields, named persons, scanned page) and the downstream handoff of the permanent page id, which the annotations cannot convey.

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?

Two short sentences, front-loaded with the core action, with the second sentence carrying the one non-obvious routing detail. No filler and nothing redundant with the schema or annotations.

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 carries the burden of explaining returns and does so at a useful level of abstraction (fields, persons, scanned page). It stops short of noting anything about the cache behavior or failure modes in prose, but nothing essential for a successful call is missing.

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 both the record address format (with two example paths) and the refresh/cache-replacement semantics are already fully documented in the schema. The description adds no meaning beyond that, which is the expected baseline for a fully documented two-parameter schema.

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 names a specific verb and resource ('Read one transcribed record') and enumerates what comes back: fields, everyone named in it, and its scanned page. That scope distinguishes it clearly from da_search_persons (search) and da_get_source (source-level), both of which appear in the sibling list.

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?

Usage is made clear indirectly: the record parameter is described as coming 'from da_search_persons', and the second sentence routes the agent onward to da_download_page once it has the page id. The flow is legible, but there is no explicit statement of when to prefer this over da_get_source or what to do if the lookup fails.

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