Skip to main content
Glama

Norwegian Company Data MCP

Get Norwegian company group

get_norwegian_company_group
Read-onlyIdempotent

The corporate group (konsern) a Norwegian company belongs to: the top parent and every subsidiary with ownership share. Accepts any member of the group.

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_group"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations stating it is read-only, the description provides significant behavioral context by defining the complexity of the return value—it returns a whole hierarchical group rather than a single entity.

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 brief and highly dense with information. Both sentences are necessary and immediately front-load the key feature: the inclusion of both parent and subsidiaries.

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

Completeness5/5

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

Since there is no output schema, the description is complete enough to inform the agent exactly what complex data structure it should expect back, making it highly actionable.

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?

Given the schema is 100% covered, the description adds value by explaining the operational context of the required 'organizationNumber' (i.e., it can be any member ID, not just the root).

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 identifies the resource being retrieved (corporate group/konsern) and defines its scope (top parent and all subsidiaries), distinguishing it from tools that might only return basic company data.

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?

It specifies that the tool accepts input for 'any member of the group,' which is a critical piece of usage guidance, letting the agent know it does not need to already know the ultimate parent to use the tool successfully.

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