Skip to main content
Glama

nordic-data

by io.github.Mnymann
OverviewDiscussionsAdmin

company_enriched

Read-onlyIdempotent

Company registry data plus national industry statistics in one call. Returns company (same shape as lookup_company) and industryStats — a time series from the national statistics office for the company's industry code (currently Danmarks Statistik for DK); industryStats.available is false when no statistics exist. Supports 4 countries: DK, NO, SE, FI. For other countries use lookup_company (basic registry data) or kyb_full (full due-diligence report).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNational company identifier — same format as lookup_company.
countryYesISO 3166-1 alpha-2 country code, lowercase. Only dk, no, se and fi are supported.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyNoRegistry data — same shape as lookup_company output.
industryStatsNoNational industry statistics (DST for DK, SSB for NO, etc.).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-2 country code, lowercase."New value: +"ISO 3166-1 alpha-2 country code, lowercase. Only dk, no, se and fi are supported."
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "dk",
-  "no",
-  "se",
-  "fi",
-  "ie",
-  "uk",
-  "fr",
-  "de",
-  "cz",
-  "pl",
-  "lv",
-  "ee",
-  "nl",
-  "be",
-  "lu"
-]New value: +[
+  "dk",
+  "no",
+  "se",
+  "fi"
+]
  2. Changed6 schema fields changed
    • removedOutput schema / properties / address
      Removed value: -{
-  "additionalProperties": true,
-  "description": "DAWA-validated address with lat/lng (or country equivalent).",
-  "properties": {
-    "formatted": {
-      "type": "string"
-    },
-    "lat": {
-      "type": "number"
-    },
-    "lon": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}
    • addedOutput schema / properties / company
      Added value: +{
+  "additionalProperties": true,
+  "description": "Registry data — same shape as lookup_company output.",
+  "type": [
+    "object",
+    "null"
+  ]
+}
    • addedOutput schema / properties / industryStats
      Added value: +{
+  "additionalProperties": true,
+  "description": "National industry statistics (DST for DK, SSB for NO, etc.).",
+  "properties": {
+    "available": {
+      "description": "False when no statistics exist for the company's industry code.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "data": {
+      "description": "Time series of {year, value, unit} rows.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "source": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}
    • removedOutput schema / properties / industry_stats
      Removed value: -{
-  "additionalProperties": true,
-  "description": "National industry statistics (DST for DK, SSB for NO, etc.).",
-  "type": "object"
-}
    • removedOutput schema / properties / registry
      Removed value: -{
-  "additionalProperties": true,
-  "description": "Same shape as lookup_company output.",
-  "type": "object"
-}
    • removedOutput schema / properties / wikidata
      Removed value: -{
-  "additionalProperties": true,
-  "description": "Public profile from Wikidata.",
-  "properties": {
-    "ceo": {
-      "type": "string"
-    },
-    "employees": {
-      "type": "number"
-    },
-    "logo": {
-      "description": "URL to company logo.",
-      "type": "string"
-    },
-    "ticker": {
-      "type": "string"
-    },
-    "website": {
-      "type": "string"
-    },
-    "wikipedia": {
-      "description": "URL to English Wikipedia article.",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, and the description adds further behavior: it returns a company object plus an industryStats time series, with industryStats.available false when no statistics exist, and names the data source (Danmarks Statistik for DK). No contradiction with annotations.

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 dense but every clause earns its place: core promise, return shape, edge-case flag, data source, country scope, and fallback routing. It remains readable and front-loaded.

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 output schema and complete parameter schema, the description provides enough extra context for correct invocation: country constraints, id format reference, the availability flag, and alternatives for unsupported countries. Nothing critical is omitted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description still adds value: it clarifies id uses the same format as lookup_company and explains the country enum values are lowercase codes for DK/NO/SE/FI only. This supplements the schema rather than repeating it.

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 opens with a specific verb/resource: 'Company registry data plus national industry statistics in one call.' It clearly distinguishes itself from siblings by naming lookup_company and kyb_full as fallbacks for other countries, so an agent can tell what this tool adds.

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 explicitly states the supported countries (DK, NO, SE, FI) and instructs: 'For other countries use lookup_company (basic registry data) or kyb_full (full due-diligence report).' This gives both when-to-use and when-not-to-use guidance with named alternatives.

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

All nordic-data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources