Skip to main content
Glama

company-identity

Company identity: name, domain, LEI, VAT, CIK or ticker to one verified legal entity — Resolves a company name, web domain, LEI, EU VAT number, SEC CIK or stock ticker to one legal entity using official free registries in a single call: GLEIF (legal name, other names, addresses, jurisdiction, registry id, direct and ultimate parent), the SEC ticker table (CIK, ticker), the EU VIES VAT service, and Companies House officers when the operator has configured a key. Deterministic matchin

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": "company-identity"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key.
leiNo20-character LEI; check digits are validated (ISO 17442).
vatNo
nameNoCompany name, with or without legal form.
domainNoCompany web domain; only used to guess a name and to prefer matching candidates. It is never fetched.
tickerNoStock ticker, matched case-insensitively against the SEC table.
countryNoISO 3166-1 alpha-2 hint; raises the score of candidates registered in that country.
max_candidatesNoHow many ranked candidates to return.
include_parentsNoLook up GLEIF direct and ultimate parents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description does useful work: it identifies the official registries queried, notes deterministic matching, states that Companies House lookup depends on a configured key, and clarifies that the domain is never fetched. It still lacks rate-limit, error, and ambiguity behavior details, but the core behavioral traits are disclosed.

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

Conciseness3/5

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

The purpose is front-loaded, but the opening phrase repeats the same idea as the following clause. The description is also truncated mid-sentence ('Deterministic matchin'), which weakens structure and polish.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex nine-parameter resolution tool with nested VAT input and no output schema, the description covers the data sources and some behavior but does not explain the returned candidate structure, ranking, or what happens when multiple matches are found. The phrase 'to one verified legal entity' is also slightly at odds with the max_candidates parameter returning multiple ranked candidates.

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 high at 89%, so the schema already documents parameter meanings and constraints. The description adds context about which registries correspond to each identifier type, but it does not add new semantics for parameters such as max_candidates or include_parents beyond what the schema provides.

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 states a specific verb and resource: resolving company identifiers to a legal entity. It names all supported identifier types and the authoritative registries used, so an agent can immediately understand the tool's function.

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?

The description implies usage for company identity resolution and lists valid identifier inputs, but it does not explicitly state when to use this tool versus alternatives or when not to use it. It also omits that at least one identifier is needed despite zero required parameters.

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