Skip to main content
Glama
Tiwas

Firmaradar

by Tiwas

Subscribe to Industry Monitoring (NACE)

firmaradar_subscribe_nace
Idempotent

Monitor Norwegian companies by NACE industry code: receive webhooks on status changes, announcements, or ownership updates. Use filters for region, size, and event type to reduce volume.

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
NameRequiredDescriptionDefault
urlNoHTTPS webhook URL that receives a POST for each matched event. Omit only if you intend to add it later via the portal.
eventsNoWhich 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.
aktivertNoWhether the subscription is active immediately (default true).
nace_codeYesThe 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_ansatteNoOptional size filter: only companies with at least this many employees.
bearer_tokenNoOptional bearer token Firmaradar sends as `Authorization: Bearer <token>` when calling your webhook URL, so your endpoint can authenticate the delivery. Stored encrypted.
fylke_filterNoOptional geographic filter: only companies in these fylker (county numbers).
kommune_filterNoOptional geographic filter: only companies in these kommuner (4-digit kommunenummer).
landsdel_filterNoOptional geographic filter: only companies in these landsdeler.
aggregation_modeNoDelivery 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_nokNoOptional size filter: only companies with at least this much revenue (NOK).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoID of the created/updated subscription.
rawNo
urlNo
eventsNo
aktivertNo
nace_codeNo
created_atNo
updated_atNo
aggregation_modeNo
aggregation_mode_enNo
Behavior5/5

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

Beyond the idempotentHint annotation, the description discloses upsert semantics on (user, nace_code), the parent-code matching all child codes, the prerequisite of a user plan with Firmaovervakning enabled, and the webhook delivery mechanism. These add substantial behavioral context not present in 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 and front-loaded, starting with the core purpose. Each sentence adds value: prerequisites, hierarchy behavior, volume reduction, idempotence, and usage context. No filler or redundancy.

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?

For an 11-parameter tool with an output schema, the description covers the essential context: what triggers events, idempotence, plan requirement, and when to call. It omits minor details like webhook authentication, but those are already in the schema. Overall, it is sufficiently complete for the tool's complexity.

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?

With 100% schema description coverage, the schema already documents all parameters. The description adds practical guidance on parameter usage, such as restricting events to status_changed, using geographic/size filters, and choosing aggregation_mode, going beyond the schema descriptions.

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 action ('Subscribe to industry (NACE) monitoring'), identifies the resource (NACE codes for Norwegian companies), and clarifies the webhook delivery. It distinguishes itself from sibling tools by focusing on industry-level monitoring rather than company-specific monitoring (e.g., add_company_monitoring).

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?

Provides explicit guidance to use list_nace_codes first and to call only when the user asks for industry monitoring. It also offers tips on filtering events and using aggregation_mode to reduce volume. However, it does not explicitly state when not to use this tool or directly mention the alternative for company-specific monitoring.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Tiwas/firmaradar-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server