Skip to main content
Glama
robobobby
by robobobby

no_company_lookup

Retrieve detailed Norwegian company information using a 9-digit organization number. This tool provides access to public business records for Norway through the mcp-nordic server.

Instructions

Look up a Norwegian company by organization number (organisasjonsnummer). Returns detailed info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
org_numberYes9-digit organization number

Implementation Reference

  • Tool registration and handler implementation for 'no_company_lookup' which fetches detailed company information by organization number from the API.
    server.tool(
      "no_company_lookup",
      "Look up a Norwegian company by organization number (organisasjonsnummer). Returns detailed info.",
      {
        org_number: z.string().describe("9-digit organization number"),
      },
      async ({ org_number }) => {
        const clean = org_number.replace(/\s/g, "");
        if (!/^\d{9}$/.test(clean)) {
          return { content: [{ type: "text", text: "Invalid org number. Must be 9 digits." }] };
        }
    
        try {
          const data = await apiFetch(`/enheter/${clean}`);
          return { content: [{ type: "text", text: formatCompanyDetail(data) }] };
        } catch (e) {
          if (e.message.includes("404")) {
            return { content: [{ type: "text", text: `No company found with org number ${clean}. Try searching sub-units (underenheter) instead.` }] };
          }
          throw e;
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the action and return type ('detailed info') but omits critical details like rate limits, authentication needs, error handling, or what 'detailed info' entails. This is insufficient for a tool with potential external API calls.

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 that front-loads the core functionality without any fluff. Every word contributes to understanding the tool's purpose, making it highly concise and well-structured.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'detailed info' includes, potential errors, or behavioral traits like idempotency or side effects. For a lookup tool that likely interacts with external data, more context is needed.

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 parameter 'org_number' is well-documented in the schema. The description adds minimal value by reinforcing it's for 'organization number' but doesn't provide additional context like format examples or validation rules beyond the schema.

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 clearly states the action ('look up'), resource ('Norwegian company'), and key identifier ('organization number'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'no_search_companies' or 'no_company_roles', which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives such as 'no_search_companies' or 'fi_company_lookup'. The description lacks context about prerequisites, exclusions, or comparative use cases, leaving the agent without direction on tool selection.

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