Skip to main content
Glama

no_company

Look up Norwegian company details by org number or name, including legal form, VAT status, bankruptcy and liquidation flags, employees, industry and address. Costs 0.002 USDC per successful x402 call.

Instructions

Norwegian company register (Brønnøysundregistrene) by org number or name: legal form, registration and founding dates, VAT registration and VAT number, bankruptcy, liquidation and forced-dissolution flags, employees, industry, address, website. Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "no_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNo1-20
nameNoName search
orgnrNo9-digit org number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the per-call price (0.002 USDC on Base), the payment protocol (x402), and the failure mode without a key (402 challenge). It does not cover rate limits, caching, or what an empty name-search returns, so a small gap remains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, purpose and geography front-loaded, followed by the field enumeration and the cost caveat. The field list is long but earns its place as a substitute for the absent output schema; nothing is redundant.

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?

Because there is no output schema, the enumerated return fields are essential and present, and the billing behavior is fully explained. Minor incompleteness remains around the 'max' parameter and the precedence of name versus orgnr, but an agent has enough to invoke it correctly.

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 already documents all three parameters and the baseline of 3 applies. The description reinforces the two query modes (org number vs name) but adds no format, syntax, or precedence detail — notably it never explains the 'max' result-limit parameter or how name and orgnr interact if both are supplied.

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 opens with a specific verb and resource — a Norwegian company register (Brønnøysundregistrene) lookup by org number or name — and enumerates the data returned (legal form, VAT, bankruptcy/liquidation flags, employees, industry, address, website). The 'Norwegian' qualifier implicitly separates it from fi_company, fr_company and uk_company, but no sibling is named explicitly, keeping it just short of the top band.

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 gives clear selection context: query by 9-digit org number or by name, and it flags the practical prerequisite that a payment key is needed or the call returns a 402 challenge. It does not give explicit exclusions (e.g. use this instead of uk_company when the entity is Norwegian), so it lacks the when-not guidance of a 5.

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