Skip to main content
Glama
robobobby
by robobobby

no_search_companies

Search the Norwegian company registry (Enhetsregisteret) by name, industry, municipality, organization form, or employee count to find business information.

Instructions

Search Norwegian company registry (Enhetsregisteret) by name, industry, municipality, or organization form

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoCompany name to search for
municipalityNoMunicipality name (e.g., 'OSLO', 'BERGEN', 'STAVANGER')
industry_codeNoNACE industry code (e.g., '62.010' for programming)
org_formNoOrganization form code (e.g., 'AS', 'ASA', 'ENK', 'NUF')
min_employeesNoMinimum number of employees
active_onlyNoOnly show active companies (not bankrupt/dissolved)
limitNoNumber of results (max 50)

Implementation Reference

  • The tool "no_search_companies" is defined here, which includes both the schema definition (inputs) and the handler logic that fetches data from the Enhetsregisteret API.
    server.tool(
      "no_search_companies",
      "Search Norwegian company registry (Enhetsregisteret) by name, industry, municipality, or organization form",
      {
        query: z.string().optional().describe("Company name to search for"),
        municipality: z.string().optional().describe("Municipality name (e.g., 'OSLO', 'BERGEN', 'STAVANGER')"),
        industry_code: z.string().optional().describe("NACE industry code (e.g., '62.010' for programming)"),
        org_form: z.string().optional().describe("Organization form code (e.g., 'AS', 'ASA', 'ENK', 'NUF')"),
        min_employees: z.number().optional().describe("Minimum number of employees"),
        active_only: z.boolean().optional().default(true).describe("Only show active companies (not bankrupt/dissolved)"),
        limit: z.number().optional().default(10).describe("Number of results (max 50)"),
      },
      async ({ query, municipality, industry_code, org_form, min_employees, active_only, limit }) => {
        const params = { size: Math.min(limit, 50) };
        if (query) params.navn = query;
        if (municipality) params["kommunenummer"] = municipality; // We'll also support name
        if (industry_code) params["naeringskode1"] = industry_code;
        if (org_form) params["organisasjonsform"] = org_form;
        if (min_employees != null) params["fraAntallAnsatte"] = min_employees;
        if (active_only) {
          params["konkurs"] = false;
          params["underAvvikling"] = false;
        }
    
        // If municipality is a name, try search with it as part of query
        const data = await apiFetch("/enheter", params);
        const units = data._embedded?.enheter || [];
    
        if (units.length === 0) {
          return { content: [{ type: "text", text: "No companies found matching your criteria." }] };
        }
    
        const total = data.page?.totalElements || units.length;
        const header = `Found ${total.toLocaleString()} companies (showing ${units.length}):\n`;
        const results = units.map((u, i) => `${i + 1}. ${formatCompanySummary(u)}`).join("\n\n");
    
        return { content: [{ type: "text", text: header + "\n" + results }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose whether this is a read-only operation, potential rate limits, authentication requirements, or what happens with partial/no matches. The mention of 'search' implies querying, but no further behavioral traits are described.

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 a single, efficient sentence with zero waste. It's front-loaded with the core purpose and lists search criteria clearly without unnecessary elaboration. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with 7 parameters, 100% schema coverage, and no output schema, the description is adequate but has gaps. It clarifies the registry source and searchable fields, but without annotations or output schema, it doesn't address behavioral aspects like result format, pagination, or error handling. Minimum viable for a read operation.

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 fully documents all 7 parameters. The description adds minimal value beyond the schema by listing searchable fields (name, industry, municipality, organization form) but doesn't provide additional syntax, format details, or usage examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the specific action ('Search Norwegian company registry') and resource ('Enhetsregisteret'), with explicit search criteria ('by name, industry, municipality, or organization form'). It distinguishes from siblings like 'no_company_lookup' (likely for specific lookups) and 'no_search_subunits' (different scope).

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

Usage Guidelines3/5

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

The description implies usage for searching Norwegian companies with various filters, but provides no explicit guidance on when to use this tool versus alternatives like 'no_company_lookup' or 'fi_search_companies'. It mentions searchable fields but doesn't specify prerequisites, exclusions, or comparative contexts with sibling tools.

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/robobobby/mcp-nordic'

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