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

norway-archives-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nb_search_inside

Read-only

Find pages in a specific book or newspaper that mention a word and get snippets; printed page numbers help you request Norway-only items from a library.

Instructions

Find the pages of one book or newspaper that mention a word, with snippets.

Works for Norway-only items too: the printed page number tells you what to request from a library even when the page cannot be shown here.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWord or name to find inside the item.
item_idYesThe item id from nb_search (32 hex characters).
max_snippetsNoMost snippets, 1 to 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses a genuinely non-obvious behavioral trait: for Norway-only items the page may not be viewable, yet the printed page number is still returned so the user can request it from a library. That is real added context. It does not say anything about result ordering, truncation, or whether snippets are complete pages.

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 sentences, front-loaded with the core capability and followed by the Norway-only caveat, with no filler. The second sentence is slightly convoluted in its phrasing but every part carries useful information.

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 adequately conveys that results are snippets tied to pages and that page numbers remain meaningful even when content is hidden. It leaves a few gaps (snippet size, no-match behavior) but nothing critical for a correct call.

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 three parameters are documented in structured data and the baseline is 3. The description only reinforces the snippet concept and that the target is a word or name; it adds no format, matching, or case-sensitivity semantics beyond the 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 (find) and a precisely scoped resource: pages of ONE book or newspaper matching a word, returning snippets. That scope distinguishes it from item-level search siblings such as nb_search, which the item_id parameter explicitly points back to.

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?

It establishes clear context for use (you already have a single item and want to locate a word inside it) and is reinforced by the schema note that item_id comes from nb_search. It offers no explicit exclusions or alternatives, and no guidance on when a full-page fetch (nb_get_page / nb_download_page) would be preferable.

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