Skip to main content
Glama

Company search, EU official registers

company_search
Read-only

Search a company name across official registers in one call: France, Sweden, Norway, Finland, Czechia and Estonia, plus GLEIF LEI records for every other country. One ranked list: register ID, legal form, city, LEI, a link to the register's own page, time read. A source that does not answer is named; the rest still answer. Use for KYB, supplier and customer checks, and facts about a European company. Example: q=Spotify. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "q": "<q>"
    },
    "name": "company_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCompany name, with or without the legal form (AB, Oy, SA, GmbH…)
limitNoResults (1-20, default 10)
countryNoOnly these countries: ISO codes or names, comma-separated (FR, SE, NO, FI, CZ, EE search their registers; any other country searches GLEIF). Default: all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / maximum
      Previous value: -9007199254740991New value: +20
    • changedInput schema / properties / limit / minimum
      Previous value: --9007199254740991New value: +1
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, non-destructive), but the description adds what they cannot: partial-failure semantics ('a source that does not answer is named; the rest still answer'), the pricing model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free), and the warning that repeats are not free, which reinforces idempotentHint=false. It also spells out the response fields (register ID, legal form, city, LEI, register link, time read) despite there being no output schema.

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?

Purpose and coverage are front-loaded, then result shape, failure behavior, use cases and pricing in a tight sequence — dense but every clause carries information an agent needs. A minor drag is the pricing/credits sentence and the slightly cryptic 'time read' phrase, which could be one clause shorter.

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 correctly takes on the burden of describing the return shape and the degradation behavior when a register fails. Scope, charge model and read-only nature together give an agent everything needed to call it correctly and understand the cost of repeating it.

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 q, limit and country are all documented in the schema with their ranges and defaults. The description only adds an example query value (q=Spotify) and restates the country scope already given in the country parameter description, 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 (search) and resource (a company name across official registers), enumerates the exact registers covered (France, Sweden, Norway, Finland, Czechia, Estonia) and the GLEIF fallback for all other countries, and describes the returned ranked list. The phrase 'in one call' implicitly separates it from the per-country siblings (fr_company, se_company, cz_company…) without needing to open any schema.

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?

Gives concrete use cases (KYB, supplier and customer checks, facts about a European company) plus a worked example (q=Spotify), which is enough context to pick this over generic siblings like search or company. It does not state when NOT to use it — e.g., a single-country lookup or a bulk KYB pack — so the routing guidance stops short of explicit exclusions.

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.