Skip to main content
Glama
Sign In
open-data-mcp

open-data-mcp

by markatdataandbeyond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

dataandbeyond--nordic-company-registry

Read-only

Search Norwegian and Finnish company registries in one call using official open APIs. Query by name, Norwegian org.nr, or Finnish Business ID to get registry data.

Instructions

Norwegian (Brønnøysund) and Finnish (PRH/YTJ) companies in one schema. Calls the official open APIs directly.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dataandbeyond--nordic-company-registry"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesNoNames, NO org.nr (9 digits) or FI Business ID (1234567-8). Example values: ["923609016","Equinor ASA"]
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
countriesNoWhich registries to search for name queries. Example values: ["NO","FI"]
maxResultsPerQueryNoMax matches per query per country Example values: 3

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description adds provenance value — 'calls the official open APIs directly' tells the agent the data is authoritative rather than scraped. It omits, however, that this spawns an Actor run which may return before completion and require polling, a significant behavioral trait only visible in the waitSecs schema field.

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 tight sentences with the schema unification benefit front-loaded and provenance second; no filler. It is arguably too terse for a four-parameter tool with async execution, but nothing written is wasted.

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

Completeness3/5

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

No output schema, but the input schema is fully documented, so parameter behavior is covered. What the description leaves out is the asynchronous Actor-run nature of the call and what a capped response looks like — an agent reading only the description could misread a partial result as a final one.

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 the schema already documents the query formats, country codes, maxResultsPerQuery, and the waitSecs polling semantics. The description adds no parameter-level guidance beyond what the schema provides, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the specific resource (Norwegian Brønnøysund and Finnish PRH/YTJ company registries) and the key value proposition of a unified schema. Implicitly differentiates from France-company-search and eu-company-verify by country scope, but never names a sibling explicitly.

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

Usage Guidelines2/5

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

No statement of when to choose this over dataandbeyond--eu-company-verify or dataandbeyond--france-company-search, and no exclusions or prerequisites. The agent must infer selection criteria purely from the country names in the description.

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