Skip to main content
Glama

pan_eu_company_lookup

Read-onlyIdempotent

[Pan-European corporate registry resolver via BRIS. Statutory verification, read-only, side-effect free]. Resolves company registration, national registry jurisdiction, European Unique Identifier (EUID) structure under Directive (EU) 2017/1132, registered office details, and statutory insolvency/liquidation warning flags. Usage: Use this tool to audit European corporate identity, legal entity status, and official national registry access points across EU Member States. Returns: JSON object with { countryCode: string, registrationNumber: string, euid: string, legalName: string, nationalRegister: object, companyStatus: string, activeInsolvencyWarning: boolean, brisInterconnectionUrl: string }.

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": {
      "countryCode": "<countryCode>",
      "registrationNumberOrVat": "<registrationNumberOrVat>"
    },
    "name": "pan_eu_company_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryCodeYes2-letter ISO country code of incorporation (e.g. IT, DE, FR, ES, NL)
companyNameHintNoOptional legal company name hint for fuzzy verification
registrationNumberOrVatYesNational commercial registry number or VAT identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so 'read-only, side-effect free' largely restates structured data; 'statutory verification' and the explicit EU Member State limitation add some value. It supplies no information on rate limits, authentication, or failure modes (e.g. what happens when an EUID cannot be resolved).

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?

The definition is compact and front-loaded, with labeled 'Usage' and 'Returns' sections that make skimming easy. The bracketed tagline partially duplicates the annotation hints, a minor redundancy, but nothing else is padding.

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?

With no output schema, the Returns line usefully enumerates the response fields, covering the read-only lookup's complexity. Parameter meaning lives in the schema, so the only remaining gap is error and edge-case behavior for unresolvable or ambiguous registrations.

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 coverage is 100%, so countryCode, registrationNumberOrVat, and companyNameHint are fully documented in the schema. The description does not add format or matching semantics beyond the schema, so the baseline of 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?

The description names a specific verb and resource: resolves company registration, national registry jurisdiction, EUID structure, registered office details, and insolvency flags via BRIS. It clearly scopes the domain to EU Member States, so an agent can immediately tell this is an EU corporate-identity resolver rather than a tax, AML, or tender tool like the listed siblings.

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?

The 'Usage' sentence gives a concrete context: auditing European corporate identity, legal entity status, and national registry access points. It does not state when NOT to use it or name any alternative tool, so the routing guidance is clear but not exhaustive.

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