Skip to main content
Glama
nordic-registry-mcp-server

nordic-registry-mcp-server

by olgasafonova

norway_get_subunit_updates

Read-only

Retrieve Norwegian branch-office registry changes since a given ISO 8601 timestamp, returning changed sub-unit organization numbers and update times for monitoring branch updates.

Instructions

Get sub-unit (branch) registry changes since a timestamp. USE WHEN: "what branches changed recently?", monitoring branch office updates. Timestamp format: ISO 8601 datetime with timezone, e.g., "2024-01-08T00:00:00Z". Returns list of changed branch org numbers with update timestamps. Not cached. FAILS WHEN: timestamp is missing or malformed. For main company updates, use norway_get_updates.

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

Input Schema

NameRequiredDescriptionDefault
sizeNoMaximum number of update entries to return; omit to let the registry apply its own default
sinceYesReturn sub-unit (branch office) registry changes recorded after this instant. ISO 8601 datetime with timezone, e.g. 2024-01-08T00:00:00Z

Output Schema

NameRequiredDescriptionDefault
updatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.1
    • changedInput schema / properties / since / description
      Previous value: -"required"New value: +"Return sub-unit (branch office) registry changes recorded after this instant. ISO 8601 datetime with timezone, e.g. 2024-01-08T00:00:00Z"
    • addedInput schema / properties / size / description
      Added value: +"Maximum number of update entries to return; omit to let the registry apply its own default"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint=false), the description discloses a concrete failure mode ('FAILS WHEN: timestamp is missing or malformed'), notes 'Not cached', and summarizes the return payload. It does not cover rate limits or pagination behavior for the size-limited result set, keeping it just under a 5.

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?

Front-loaded with purpose, then clearly delimited USE WHEN / FAILS WHEN / alternative segments — easy to scan. The ISO 8601 format example appears twice, which is minor redundancy that keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema and full annotation coverage, the description only needs to supply purpose, routing, and failure conditions — all of which are present. Nothing an agent needs to invoke this tool correctly is missing.

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 both parameters are already documented, and the description's ISO 8601 example largely repeats the schema text for 'since'. The optional 'size' parameter is not addressed at all in the description, so no meaning is added beyond structured fields.

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: 'Get sub-unit (branch) registry changes since a timestamp.' It immediately distinguishes the scope (branch/sub-unit) from the main-company sibling later in the text, so an agent can route between them without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'USE WHEN' clause gives a natural-language trigger ('what branches changed recently?') plus a monitoring scenario, and the final sentence names the alternative tool ('For main company updates, use norway_get_updates') with the condition that selects it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.