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

norway-archives-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

place_names

Read-only

Search Kartverket's place-name register for farms, hamlets, lakes, and places; get current spelling, type, municipality, and coordinates. Use wildcards or fuzzy matching for old record spellings.

Instructions

Find farms, hamlets and other places in Kartverket's official place-name register.

Gives today's spelling, type (farm, village, lake…), municipality and coordinates. Old spellings in records often differ: try a wildcard or fuzzy.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe name; * is a wildcard, e.g. 'Røros*'.
fuzzyNoAlso return names that sound alike.
limitNoMost names, 1 to 100.
countyNoToday's county: name or number.
municipalityNoToday's municipality: name or number (merged since 2020).

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 only declare readOnlyHint and openWorldHint, so the description carries the rest of the burden and does add value by naming what comes back (today's spelling, type, municipality, coordinates), which matters since there is no output schema. It stops short of describing credentials, rate limits, or result ordering.

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, zero waste, and the resource and return fields are front-loaded before the fallback search advice. Every clause earns its place.

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?

For a five-parameter read-only lookup with no output schema, the definition covers purpose, returned fields, and search strategy, and the schema handles the rest. Only minor gaps remain, such as whether results are ranked or paginated beyond the explicit limit.

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 coverage is 100%, with each parameter already documented, including the * wildcard and the fuzzy 'sounds alike' behavior, so the baseline is 3. The description adds only the rationale that historical spellings diverge, not new syntax or constraints 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?

States a specific verb (find) plus the resource (farms, hamlets and other places) and names the authoritative dataset, Kartverket's official place-name register. An agent knows immediately this is an official geographic-name lookup and cannot confuse it with the Digitalarkivet/National Library siblings.

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?

Gives concrete search strategy tied to a real condition: old spellings in records often differ, so try a wildcard or fuzzy. That is clear when-to-use guidance for the two search modifiers, though it offers no explicit exclusions or prerequisites because no sibling covers this resource.

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