GlobalEntity API

Find Norwegian companies by growth, revenue, size and location

find_companies

Read-onlyIdempotent

List Norwegian companies matching filters: revenue growth vs the previous year (%), revenue (NOK), employees, county (fylke), municipality, industry (NACE) and legal form. Returns name, org. number, industry, address, employees and the latest filed accounts (revenue for 3 years, growth %, operating result, equity) from Brønnøysundregistrene, plus the total number of matches. Growth is measured from a previous-year revenue of at least 1 MNOK unless revenue_prev_min is set.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_companies"
  }
}

Input Schema

Name	Required	Description
`name`	No	Optional part of the company name.
`sort`	No	Sort order (default: growth when growth is filtered, else revenue when revenue is filtered, else employees).
`limit`	No	Maximum results (default 20).
`county`	No	Norwegian county (fylke) name or number, e.g. Akershus, Oslo, Vestland, Rogaland, 32.
`offset`	No	Skip this many results (paging).
`legal_form`	No	Legal form code, e.g. AS, ASA, ENK, NUF.
`municipality`	No	Municipality (kommune) name or 4-digit number, e.g. Bergen or 4601.
`employees_max`	No	Maximum number of employees.
`employees_min`	No	Minimum number of employees.
`industry_nace`	No	NACE code or prefix, e.g. 62 (IT), 43.2 (electrical/plumbing), 69.2 (accounting).
`revenue_max_nok`	No	Maximum revenue in NOK.
`revenue_min_nok`	No	Minimum revenue (driftsinntekter) in NOK for the latest filed year, e.g. 20000000.
`revenue_prev_min_nok`	No	Minimum previous-year revenue in NOK for growth filters (default 1000000; 0 = no minimum).
`revenue_growth_max_pct`	No	Maximum revenue growth in % (use a negative number to find declining companies, e.g. -10).
`revenue_growth_min_pct`	No	Minimum revenue growth vs the previous year in %, e.g. 20.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and open-world. The description adds meaningful context beyond that: it names the data source (Brønnøysundregistrene), lists the returned fields including multi-year accounts and total matches, and clarifies the default growth-measurement threshold. This is solid behavioral disclosure without contradicting annotations.

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 front-loaded with the core action and filter dimensions, then moves to return values and a caveat about growth measurement. It is dense but efficient for a 15-parameter tool, with no obviously wasted sentences.

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?

Given 15 parameters and no output schema, the description does the necessary work of describing return fields, the data source, and the total-match count. It stops short of explaining pagination behavior or differentiating from sibling tools, but the core calling context is sufficiently covered.

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 description coverage is 100%, so the schema already documents all 15 parameters thoroughly. The description enumerates the same filter dimensions (revenue growth, revenue, employees, county, municipality, NACE, legal form) but adds little syntax or interpretation beyond what the schema provides, aside from reinforcing the growth threshold rule.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource — 'List Norwegian companies matching filters' — and enumerates the filter dimensions, so the basic purpose is unmistakable. However, it does not distinguish this tool from the sibling search_companies, so an agent must infer when to choose one over the other.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what filters exist but provides no explicit guidance on when to use this tool versus search_companies or other siblings. There are no exclusions, prerequisites, or alternative-selection cues, leaving the agent to guess the intended usage context.

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

All GlobalEntity API tools Inspect

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

Need Help?