Skip to main content
Glama
Tiwas

Firmaradar

Search Companies

firmaradar_search_companies
Read-onlyIdempotent

Find Norwegian companies using filters like name, industry, location, status, size, and founding date. Returns a paginated list of candidate organization numbers for further investigation.

Instructions

Search Norwegian companies with filters (name, NACE, location, status, size, founding date). Returns paginated list of candidate orgnr to investigate further. Use when you have a description and need to find matching companies; use get_company once you have a specific orgnr.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search across company names.
naceNoNACE 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: '47' matches all retail (2-digit), '47.1' matches food/beverage retail (3-digit), '47.11' matches grocery stores (4-digit), '47.111' is the most specific (5-digit). If a 4-digit code yields no results, try appending '0' for the 5-digit form (e.g. '56.110' instead of '56.10').
kommuneNoNorwegian 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.
fylkeNoNorwegian fylkenummer — EXACTLY 2 digits, zero-padded. Examples: '03' = Oslo, '11' = Rogaland, '15' = Møre og Romsdal. Fylke-NAMES are NOT accepted — translate first.
statusNoFilter on company status.
min_ansatteNo
max_ansatteNo
min_omsetning_nokNo
max_omsetning_nokNo
stiftet_etterNoISO 8601 date — only companies founded on/after.
stiftet_forNoISO 8601 date — only companies founded on/before.
limitNo
cursorNoOpaque pagination cursor from previous call.
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds context about paginated list and candidate identifiers but no behavioral contradictions.

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?

Three sentences, front-loaded with purpose and result, clear usage guidance, no unnecessary words.

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?

Despite 13 parameters and no output schema, description provides sufficient context for search tool: what it does, what it returns, and usage guidance. Complex enough tool handled well.

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 coverage is 62% with parameter descriptions; tool description only summarizes filter types without new parameter details, so baseline of 3 is appropriate.

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?

Description clearly states it searches Norwegian companies with various filters, returns paginated list of orgnr candidates, and distinguishes from sibling like get_company.

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?

Explicitly advises when to use this tool (when description needed to find companies) and when to use get_company (after specific orgnr).

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