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

norway-archives-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

da_get_source

Read-only

Retrieve a Norwegian archival source by ID and map its sections to the scanned image where each list begins, helping locate baptisms, confirmations, migrations, and other records.

Instructions

Describe one source and map its scans: archive reference, images, where each list starts.

Sections are the lists in the book (baptisms, confirmations, out-migrated…) with the image each begins on; a list usually runs until the next starts.

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": {
      "source_id": "<source_id>"
    },
    "name": "da_get_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoTrue asks again instead of using the cached answer, and replaces it.
source_idYesThe source id, from da_search_sources or a record.

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 readOnlyHint and openWorldHint, so the safety profile is covered; the description goes further by disclosing the shape of the payload (archive reference, image mapping, per-section start images). It does not discuss cost, latency, or failure modes, but for a read-only lookup the added structural detail is substantial.

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?

Two short sentences with the main action front-loaded and the second sentence devoted entirely to clarifying 'sections'. The parenthetical examples (baptisms, confirmations, out-migrated) earn their space by disambiguating an unfamiliar domain term.

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 must carry return-value meaning, and it does so by naming the fields the agent will receive and explaining how section→image mapping works. Gaps are minor: nothing on empty results, invalid IDs, or how large a book's image list typically is.

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% and the schema already explains both source_id (origin: da_search_sources or a record) and refresh (cache replacement). The description adds no parameter-level meaning, so the baseline of 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?

States a specific verb+resource ('Describe one source and map its scans') and enumerates what the answer contains: archive reference, images, and where each list starts. An agent can tell it is a single-source detail/retrieval tool rather than a search, though no sibling is named for contrast.

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?

There is no explicit when-to-use or when-not-to-use statement and no alternative is named. Usage is only implied by the content ('map its scans', 'where each list starts'), which suggests the agent should call it to orient itself before fetching or downloading images.

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