Firmaradar

Overview Schema Source Related Servers Discussions Admin

List Companies by Industry (NACE)

firmaradar_list_companies_in_nace

Read-onlyIdempotent

List Norwegian companies by NACE code or prefix, with optional filters for status, municipality, and employee count, for sector analysis.

Instructions

List Norwegian companies in a specific NACE industry code (or code prefix), optionally filtered by status, kommune and size. Useful for sector analysis ('all active restaurants in Oslo with > 5 employees').

NACE format warning: Use the EU NACE Rev. 2 format with a trailing zero (e.g. 62.100, 62.200, 58.290). The Norwegian SN2007 format (62.01, 62.02) returns 0 hits — we do not store SN2007. If you are unsure about a code, call firmaradar_list_nace_codes first. Backed by the official Norwegian register (BRREG) and refreshed daily. Use stiftet_etter for newly-founded-company queries.

Input Schema

TableJSON Schema

Name	Required	Description
`code`	Yes	NACE code or prefix. Norwegian BRREG uses 5-digit SN2007 codes internally (e.g. '56.110' for restaurants, '47.111' for grocery stores). Any prefix works: '56' matches all serving (2-digit), '56.1' matches restaurants/cafes (3-digit), '56.11' matches restaurant operations (4-digit), '56.110' matches the most specific level (5-digit). If a 4-digit code yields no results, try appending '0' (e.g. '56.110' instead of '56.10').
`limit`	No
`cursor`	No
`status`	No
`kommune`	No	Norwegian kommunenummer — EXACTLY 4 digits, zero-padded. Examples: '0301' = Oslo, '4601' = Bergen, '5001' = Trondheim, '1103' = Stavanger. Kommune-NAMES are NOT accepted — translate the name to kommunenummer first.
`max_ansatte`	No
`min_ansatte`	No
`stiftet_for`	No	ISO 8601 date (YYYY-MM-DD) — only companies founded on/before this date.
`stiftet_etter`	No	ISO 8601 date (YYYY-MM-DD) — only companies founded on/after this date. Use for 'newly founded companies in this industry' queries (industry monitoring).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`catalog`	No
`nace_code`	Yes
`next_cursor`	No
`total_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.1.2Jul 31, 2026

addedInput schema / properties / stiftet_etter

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ISO 8601 date (YYYY-MM-DD) — only companies founded on/after this date. Use for 'newly founded companies in this industry' queries (industry monitoring).",
+  "title": "Stiftet Etter"
+}

addedInput schema / properties / stiftet_for

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ISO 8601 date (YYYY-MM-DD) — only companies founded on/before this date.",
+  "title": "Stiftet For"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "NaceCatalogInfo": {
+      "description": "Aggregat-counts fra ``nace_code`` (oppdateres nattlig).\n\nDet totale antallet norske selskaper i koden, splittet i aktive (ikke\nkonkurs/avvikling) og total (alle inkl. konkurs/avvikling). Disse er\nrullet opp i NACE-hierarkiet, så også foreldre-koder (eks. ``62``,\n``62.1``, ``62.10``) har realistiske counts.\n\n``company_count`` er en legacy-alias for ``company_count_active`` for\nback-compat — den eldre API-en lagret kun aktive selskaper i denne\nkolonnen.",
+      "properties": {
+        "company_count": {
+          "title": "Company Count",
+          "type": "integer"
+        },
+        "company_count_active": {
+          "title": "Company Count Active",
+          "type": "integer"
+        },
+        "company_count_total": {
+          "title": "Company Count Total",
+          "type": "integer"
+        },
+        "label_no": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Label No"
+        },
+        "level": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Level"
+        },
+        "parent_code": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Parent Code"
+        }
+      },
+      "required": [
+        "company_count",
+        "company_count_active",
+        "company_count_total"
+      ],
+      "title": "NaceCatalogInfo",
+      "type": "object"
+    },
+    "NaceCompanyHit": {
+      "properties": {
+        "antall_ansatte": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Antall Ansatte"
+        },
+        "kommune": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Kommune"
+        },
+        "naeringskode": {
+          "title": "Naeringskode",
+          "type": "string"
+        },
+        "navn": {
+          "title": "Navn",
+          "type": "string"
+        },
+        "orgnr": {
+          "title": "Orgnr",
+          "type": "string"
+        },
+        "status": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Status"
+        },
+        "stiftelsesdato": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Stiftelsesdato"
+        }
+      },
+      "required": [
+        "orgnr",
+        "navn",
+        "naeringskode"
+      ],
+      "title": "NaceCompanyHit",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "catalog": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/NaceCatalogInfo"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "items": {
+      "items": {
+        "$ref": "#/$defs/NaceCompanyHit"
+      },
+      "title": "Items",
+      "type": "array"
+    },
+    "nace_code": {
+      "title": "Nace Code",
+      "type": "string"
+    },
+    "next_cursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Next Cursor"
+    },
+    "total_count": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Total Count"
+    }
+  },
+  "required": [
+    "nace_code",
+    "items"
+  ],
+  "type": "object"
+}

First observedv0.1.0May 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. The description adds high-value behavioral disclosure: the EU NACE Rev. 2 trailing-zero requirement, the warning that SN2007 format returns 0 hits, the BRREG data source, and daily refresh frequency. This goes well beyond the annotations and shapes agent behavior.

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?

The description is moderately long but every sentence earns its place: the example, format warning, alternative-tool pointer, and data-source note are all actionable. Bold text and a clean structure make it scannable without being verbose.

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?

With an output schema present, return values are already documented. The description covers the crucial NACE-format trap, data freshness, and a concrete use case, which is sufficient for a 9-parameter tool. It could mention pagination behavior more explicitly, but the schema's cursor parameter and output schema reduce the need.

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 description coverage is only 44%, but the description compensates by explaining NACE format in context and pointing to stiftet_etter for new-company queries. It also gives a concrete example that maps to status, kommune, and min_ansatte. It doesn't elaborate on limit or cursor, but those are straightforward and the schema provides enough defaults.

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 uses a specific verb ('List') with a clear resource ('Norwegian companies in a specific NACE industry code') and mentions optional filters, giving the agent a precise picture. It also distinguishes itself from a sibling tool by referencing firmaradar_list_nace_codes for code lookups, which prevents confusion about scope.

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?

The description provides concrete usage context with a sector-analysis example ('all active restaurants in Oslo with > 5 employees') and advises calling firmaradar_list_nace_codes when unsure about a code. It also recommends stiftet_etter for newly-founded-company queries. It does not explicitly contrast with firmaradar_search_companies, but the guidance is clear enough for correct selection.

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

Deploy Server