Skip to main content
Glama

EU Business & VAT Checker

Search a French SIREN or Norwegian register

lookup_company_registry
Read-onlyIdempotent

Use this when the user asks about a company registered in France or Norway, or for the company registration number on a Kbis extract, for example "find the French company Danone", "who is behind SIREN 552032534?" or "look up Equinor in the Norwegian business register". Pass country FR or NO and the company name or its registration number (SIREN for France, organisation number for Norway). Returns the legal name, registration number, legal form, status (active, ceased, bankrupt, being wound up), registration date, registered address, activity code and, where published, size or employee count. Sole proprietors are left out. Do not use it for other countries, for owners, directors or any private person, or for accounts and credit ratings.

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": {
      "country": "<country>",
      "query": "<query>"
    },
    "name": "lookup_company_registry"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost entities to return. Default 5.
queryYesCompany name, or the registration number: SIREN (9 digits) for FR, organisation number (9 digits) for NO.
countryYesRegister to search: FR (France, Sirene) or NO (Norway, Enhetsregisteret). Other countries are not covered.

Output Schema

NameRequiredDescriptionDefault
noteNo
queryYes
noticeYes
sourceYes
countryYes
entitiesYes
totalMatchesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / entities / items / properties / employeeRange
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / entities / items / properties / employeeYear
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / entities / items / properties / foundedOn
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • removedOutput schema / properties / note_from_openkrill
      Removed value: -{
      -  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • addedOutput schema / properties / note_from_openkrill
      Added value: +{
      +  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description adds coverage details beyond them, notably that sole proprietors are excluded and precisely which registers are searched. It doesn't discuss rate limits or result freshness, but the scope disclosure is meaningful.

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?

Front-loaded with the usage trigger and clearly organized into when-to-use, inputs, outputs, and exclusions. Slightly repetitive in restating registration-number formats already in the schema, but no sentence is wasteful.

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?

Even though an output schema exists (so return fields needn't be enumerated), the description still lists returned fields and states exclusions, making the tool fully callable without opening either schema.

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 country, query and limit. The description restates the country codes and number formats (SIREN 9 digits FR, organisation number NO) without adding syntax the schema lacks, so baseline 3 applies.

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?

States a specific verb (lookup) and resource (company registry) and immediately scopes it to France's SIREN and Norway's register. A sibling like find_company_lei or check_vat_number is clearly separable from this registry-lookup tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete trigger examples ("find the French company Danone", "who is behind SIREN 552032534?") plus explicit exclusions: other countries, owners/directors/private persons, accounts and credit ratings. This is a full when/when-not statement.

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.