Firmaradar

Overview Schema Source Related Servers Discussions Admin

Subscribe to Industry Monitoring (NACE)

firmaradar_subscribe_nace

Idempotent

Monitor Norwegian companies by NACE code and receive webhook alerts for bankruptcies, new filings, and ownership changes. Use filters for event type, geography, and company size to reduce noise.

Instructions

Subscribe to industry (NACE) monitoring: when any Norwegian company in the chosen industry triggers a monitored event (new announcement, status change such as bankruptcy/dissolution, or ownership update), Firmaradar delivers a webhook to your URL. Use list_nace_codes first to resolve the exact code. A subscription on a parent code matches all child codes. Restrict events (e.g. ['status_changed']) and use geographic/size filters to cut volume in large industries, or pick a digest aggregation_mode. Idempotent — upserted on (user, nace_code), so re-subscribing the same code updates it. Requires a user whose plan has Firmaovervakning enabled. Call only when the user has asked to set up industry monitoring.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No	HTTPS webhook URL that receives a POST for each matched event. Omit only if you intend to add it later via the portal.
`events`	No	Which event types to deliver. Omit for all of them. Restrict to e.g. ['status_changed'] to receive only bankruptcy/dissolution signals and cut volume dramatically in large industries.
`aktivert`	No	Whether the subscription is active immediately (default true).
`nace_code`	Yes	The NACE code to monitor. Accepts a section letter ('G'), a group ('47'), or a more specific code ('47.110'). Resolve the exact code first with list_nace_codes if unsure. A subscription on a parent code also matches events in all child codes.
`min_ansatte`	No	Optional size filter: only companies with at least this many employees.
`bearer_token`	No	Optional bearer token Firmaradar sends as `Authorization: Bearer <token>` when calling your webhook URL, so your endpoint can authenticate the delivery. Stored encrypted.
`fylke_filter`	No	Optional geographic filter: only companies in these fylker (county numbers).
`kommune_filter`	No	Optional geographic filter: only companies in these kommuner (4-digit kommunenummer).
`landsdel_filter`	No	Optional geographic filter: only companies in these landsdeler.
`aggregation_mode`	No	Delivery cadence. 'real_time' (default) posts each event immediately. 'hourly_digest' / 'daily_digest' batch events to reduce noise in high-volume industries.	real_time
`min_omsetning_nok`	No	Optional size filter: only companies with at least this much revenue (NOK).

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	ID of the created/updated subscription.
`raw`	No
`url`	No
`events`	No
`aktivert`	No
`nace_code`	No
`created_at`	No
`updated_at`	No
`aggregation_mode`	No
`aggregation_mode_en`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.3Aug 1, 2026

removedInput schema / properties / events / anyOf

Removed value: -[
-  {
-    "items": {
-      "enum": [
-        "created",
-        "updated",
-        "deleted",
-        "status_changed"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / events / default
```
Removed value: -null
```

addedInput schema / properties / events / items

Added value: +{
+  "enum": [
+    "created",
+    "updated",
+    "deleted",
+    "status_changed"
+  ],
+  "type": "string"
+}

addedInput schema / properties / events / type
```
Added value: +"array"
```

Addedv0.1.2Jul 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (idempotentHint=true), the description explains the upsert-on-(user, nace_code) behavior, parent-code child-code matching, plan requirement (Firmaovervakning), webhook POST behavior, and optional bearer token. This adds substantial behavioral context not present in the structured 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 compact yet information-dense, with every sentence providing actionable guidance. It is front-loaded with the core purpose and then efficiently covers prerequisites, matching behavior, filtering, idempotency, and permissions without redundancy.

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?

For an 11-parameter subscription tool, the description covers all key aspects: what events are monitored, how to use NACE codes, filtering strategies, aggregation modes, authorization, idempotency, and prerequisites. With an output schema present, not detailing return values is acceptable, and the description still gives a complete operational picture.

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%, and each parameter already has a descriptive schema entry. The description adds extra strategic semantics, such as 'restrict events to cut volume', 'use geographic/size filters to cut volume', and parent-code expansion, which enriches beyond the raw schema.

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 ('Subscribe to industry (NACE) monitoring') and clearly states the resource (industry/NACE codes) and the delivery mechanism (webhook on monitored events). It differentiates from sibling tools like firmaradar_add_company_monitoring by focusing on industry-level rather than company-level monitoring.

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?

The description gives explicit usage guidance: call list_nace_codes first to resolve codes, call only when the user requests industry monitoring, restrict events and use filters for high-volume industries, and choose aggregation_mode for digest delivery. It also implies a clear alternative by contrasting with company monitoring via its title and scope.

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

Deploy Server