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

norway-archives-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

da_list_pages

Read-only

Lists a source's scanned pages in order with permanent IDs and permalinks so you can locate page IDs for downloading untranscribed records.

Instructions

List a source's scanned pages in order, with each page's permanent id and permalink.

For reading a list nobody transcribed: pass page ids 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": {
      "source_id": "<source_id>"
    },
    "name": "da_list_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many images, at most 100.
startNoFirst image number, 1-based.
refreshNoTrue asks again instead of using the cached answer, and replaces it.
sectionNoStart where this list begins instead (code or label, e.g. kf).
source_idYesThe source id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 that results are ordered and include a permanent id plus permalink, which is useful given there is no output schema, but it says nothing about caching, rate limits, or what happens when the source has no pages.

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 with no filler; the core purpose and returned fields are front-loaded, and the workflow hint comes second.

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 five params fully documented in the schema and no output schema, the description is nearly complete: it names the returned fields and the natural next step. It only omits edge-case behavior such as empty sources or how caching interacts with refresh.

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 count, start, refresh, section, and source_id are all documented in the schema itself. The description adds no parameter-level meaning beyond implying that ids from this list feed into da_download_page.

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?

States a specific verb and resource ('List a source's scanned pages in order') and names exactly what each entry carries (permanent id and permalink), so an agent knows this is a paged metadata listing rather than a content fetch or a search.

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?

The second sentence gives explicit follow-up guidance: when a list is untranscribed, pass the page ids to da_download_page. It clarifies the downstream use but offers no explicit 'when not to use this' or contrast with other listing/search siblings.

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