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

norway-archives-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nb_search

Read-only

Search the National Library of Norway's books, newspapers, journals, maps and other collections by title or full text, filter by publication year and media type, and see where each item can be read.

Instructions

Search the National Library of Norway's books, newspapers and more.

Each item says where it can be read: everywhere, Norway only, or the library only. nb_search_inside finds the page in any of them.

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": {
      "query": "<query>"
    },
    "name": "nb_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, 20 items each.
queryYesWords to find; quotes for a phrase, e.g. '"Røros kobberverk"'.
refreshNoTrue asks again instead of using the cached answer, and replaces it.
year_toNoLatest year of publication.
full_textNoSearch inside the text, not only titles.
year_fromNoEarliest year of publication.
media_typeNobooks, newspapers, journals, maps, letters, manuscripts, pictures, private archives; empty for all.books
digitised_onlyNoOnly digitised items.

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 and openWorldHint, so the safety profile is covered. The description adds genuinely useful result-level behavior that annotations cannot convey: every hit carries an access tier (everywhere, Norway only, library only), which tells the agent upfront that some results are geographically or physically restricted. It omits rate-limit or result-volume behavior, but the caching hint lives in the refresh parameter.

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?

Three short sentences with the scope, the availability caveat, and the sibling hand-off in that order — no filler and nothing repeated from the schema.

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 eight fully documented parameters, no output schema, and a read-only open-world profile, the description covers what an agent needs to call it and to interpret access-limited hits. Only minor gaps remain, such as expected result volume or pagination behavior beyond the page parameter.

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%, including phrase-quoting syntax for query, media_type options, and year bounds, so the schema carries the parameter burden. The description adds no parameter-level detail beyond what is already documented, which is the expected baseline when coverage is complete.

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 (search the National Library of Norway's books, newspapers and more) and immediately names the sibling it is not: nb_search_inside is the page-finder. An agent can route between the two without opening either schema.

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 implies the practical selection criterion: use this tool to discover items, then use nb_search_inside to reach a page inside them. That is clear contextual routing, but there are no explicit exclusions or guidance on when a different sibling (e.g. a records or persons search) would be the better entry point.

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