Skip to main content
Glama
robobobby
by robobobby

no_company_roles

Retrieve board members, CEO, auditor, and other roles for Norwegian companies using their 9-digit organization number.

Instructions

Get roles (board members, CEO, auditor, etc.) for a Norwegian company

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
org_numberYes9-digit organization number

Implementation Reference

  • The implementation and registration of the 'no_company_roles' tool, which fetches roles from the Norwegian Brønnøysund Register Centre API.
    server.tool(
      "no_company_roles",
      "Get roles (board members, CEO, auditor, etc.) for a Norwegian company",
      {
        org_number: z.string().describe("9-digit organization number"),
      },
      async ({ org_number }) => {
        const clean = org_number.replace(/\s/g, "");
        const res = await fetch(`https://data.brreg.no/enhetsregisteret/api/enheter/${clean}/roller`, {
          headers: { Accept: "application/json", "User-Agent": USER_AGENT },
        });
    
        if (!res.ok) {
          if (res.status === 404) {
            return { content: [{ type: "text", text: `No roles found for org number ${clean}.` }] };
          }
          throw new Error(`API error (${res.status})`);
        }
    
        const data = await res.json();
        const groups = data.rollegrupper || [];
    
        if (groups.length === 0) {
          return { content: [{ type: "text", text: "No role information available for this company." }] };
        }
    
        const lines = [`**Roles for ${clean}:**\n`];
        for (const group of groups) {
          lines.push(`## ${group.type?.beskrivelse || "Unknown"}`);
          for (const role of group.roller || []) {
            const person = role.person;
            const org = role.enhet;
            if (person) {
              const name = [person.fornavn, person.mellomnavn, person.etternavn].filter(Boolean).join(" ");
              lines.push(`- ${name} (${role.type?.beskrivelse || "?"})${role.fratraadt ? " [resigned]" : ""}`);
            } else if (org) {
              lines.push(`- ${org.organisasjonsnummer} ${org.organisasjonsform?.kode || ""} (${role.type?.beskrivelse || "?"})`);
            }
          }
          lines.push("");
        }
    
        return { content: [{ type: "text", text: lines.join("\n") }] };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's a 'Get' operation (implying read-only), but doesn't clarify permissions, rate limits, error conditions, or response format. For a tool with no annotations, this leaves significant gaps in understanding how it behaves.

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 purpose. Every word earns its place by specifying the action, resource type, and geographic scope without redundancy or fluff.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what the return values look like (e.g., list of roles with details), potential errors, or operational constraints. For a tool that presumably returns structured data, this lack of output information is a significant gap.

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%, with the single parameter 'org_number' fully documented as a '9-digit organization number'. The description adds no additional parameter semantics beyond implying the tool uses this to identify a Norwegian company. This meets the baseline of 3 for high schema coverage.

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 ('Get roles') and target resource ('for a Norwegian company'), specifying the types of roles (board members, CEO, auditor, etc.). It distinguishes from most siblings by focusing on company roles rather than weather, addresses, or general company lookups. However, it doesn't explicitly differentiate from 'no_company_lookup' which might also retrieve company information.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an org_number), exclusions, or comparisons with sibling tools like 'no_company_lookup' or 'no_search_companies'. The agent must infer usage from the purpose alone.

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