Skip to main content
Glama

Norwegian Company Data MCP

Get Norwegian company

get_norwegian_company
Read-onlyIdempotent

Full profile of one Norwegian company by organisation number: register details, contact information, activity, CEO, board, auditor and accountant, and the latest filed revenue and profit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationNumber": "<organizationNumber>"
    },
    "name": "get_norwegian_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationNumberYesNine-digit Norwegian organisation number, such as 923609016.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description still adds value by disclosing the substantive payload (board, auditor, accountant, latest filed revenue/profit) which an agent could not infer from annotations, though it is silent on not-found handling and data freshness beyond 'latest filed'.

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?

One dense sentence, front-loaded with the operation and key, followed by the returned field groups. No filler and nothing wasted.

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?

With no output schema, the enumeration of returned sections is the right compensating detail and makes the tool callable with confidence. The remaining gap is sibling overlap — an agent cannot tell from this description whether financials require a separate call.

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% and the single parameter has a pattern plus an example (923609016), so the schema already does the work. The description only restates that lookup is keyed on organisation number, adding no format or validation detail beyond the schema — baseline 3.

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?

States a specific verb+resource ('Full profile of one Norwegian company') and enumerates exactly what is returned: register details, contact, activity, CEO, board, auditor, accountant, revenue and profit. It does not, however, distinguish itself from the sibling get_norwegian_company_financials, which presumably also returns revenue/profit.

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 'by organisation number' phrasing implies a direct single-record lookup, so intended usage is inferable. But there is no explicit when-to-use guidance, no mention of when to prefer get_norwegian_company_financials or get_norwegian_company_group, and no statement about behavior for unknown organisation numbers.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources