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

nordic-registry-mcp-server

by olgasafonova

norway_get_updates

Read-only

Track main company registry changes in Norway since a given ISO 8601 timestamp, returning organization numbers with update times to answer recent-change questions.

Instructions

Monitor main company registry changes since a timestamp. USE WHEN: "what companies changed recently?", "registry updates". Timestamp format: ISO 8601 datetime with timezone, e.g., "2024-01-08T00:00:00Z". Not cached. Returns list of org numbers with update timestamps. FAILS WHEN: timestamp is missing or malformed. For branch office changes only, use norway_get_subunit_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_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoMaximum number of update entries to return; omit to let the registry apply its own default
sinceYesReturn main-unit 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 main-unit 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.5/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, and non-idempotent behavior. The description adds useful context that results are not cached, that a timestamp is required, and that malformed or missing timestamps fail, though it does not describe rate limits or pagination behavior for the size 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?

The description is front-loaded and compact, with usage, failure modes, and the relevant sibling alternative stated without unnecessary wording.

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 the annotations, complete parameter schema, and output schema, the description includes everything essential for correct tool selection and invocation. It covers the main use case, timestamp requirements, failure behavior, and the key alternative tool.

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 in the input schema. The description reinforces the timestamp format but does not add meaning beyond the schema for the optional size parameter.

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 states a specific verb and resource: monitoring main company registry changes since a timestamp. It clearly distinguishes this from branch-office updates by naming norway_get_subunit_updates.

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?

It gives explicit USE WHEN examples and names the alternative tool for branch office changes. The required timestamp format and failure condition further make the usage boundary clear.

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