GlobalEntity API

Search a national company register

search_companies

Read-onlyIdempotent

Search an official national business register by company name or registration number. Returns name, registration number, status, legal form, industry (NACE), address, registration date, VAT flag and LEI. A 20-character LEI in query is resolved globally.

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": "search_companies"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results (default 10).
`query`	Yes	Company name or registration number.
`country`	Yes	Country name or ISO code, e.g. Norway, NO, Denmark, Germany, United Kingdom.
`active_only`	No	Only return active (not dissolved) companies.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context on top: the exact result payload and the cross-border LEI resolution path, i.e. the tool may escape the country scope the agent supplied. It stops short of covering result caps beyond the schema's limit.

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?

Two sentences, zero filler. Capability and scope come first, the result contract second, and the LEI edge case is appended where it will be read.

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?

With no output schema, the description carries the return-value burden and discharges it by naming every field. Combined with annotations covering safety and a fully described input schema, an agent has what it needs to call this correctly; pagination nuances are the only minor 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% and all four parameters are documented there, so the baseline is 3. The description restates name-or-registration-number input and contributes one genuinely new semantic — that an LEI query is resolved globally rather than within the given country.

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?

States a specific verb and resource ("Search an official national business register") plus the two lookup keys, and enumerates the returned fields, so an agent knows exactly what it gets. It does not distinguish itself from plausible siblings such as resolve_company or verify_identifier, leaving that differentiation to the agent.

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

Usage Guidelines3/5

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

Usage is implied by the inputs: pass a company name or registration number plus a country. The one explicit routing rule is partial — a 20-character LEI in query is resolved globally — but there is no statement of when to prefer this over resolve_company, or what to do with a non-matching country.

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

All GlobalEntity API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?