Skip to main content
Glama

Company lei

company_lei
Read-onlyIdempotent

Use when an agent needs to verify a company or find its LEI: by lei= the legal name, status, legal form, addresses, registration renewal date, direct and ultimate parent and BIC. Returns the paid x402 request for your input (GET /company/lei, $0.005 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.

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_lei"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiNo20-character Legal Entity Identifier (ISO 17442). Give lei or name.
nameNoCompany name to search (2-100 characters); returns up to 10 ranked matches. Give lei or name.
countryNoOptional 2-letter ISO country of the legal address to narrow a name search, e.g. DE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare read-only/open-world/idempotent; the description adds substantially more: the call returns a paid x402/MPP request rather than data, the endpoint GET /company/lei, $0.005 per call, validation refusing bad input before any charge, and a free first call each day. Those are exactly the non-obvious behaviors an agent must plan around for a paid two-step flow.

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 trigger, then the return value, then the payment mechanics; every sentence carries information. The 'by lei=' construction is garbled and the payment/charge rules take three sentences that could be tightened.

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?

No output schema exists, and the description compensates by listing returned fields and explaining the pricing/response protocol. It still leaves the exact shape of the returned request (and what the daily-free payload looks like) implicit, which for a paid tool is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3; the description still adds meaning by indicating that a lei lookup returns entity detail fields and that name search is a lookup path. The phrasing 'by lei=' is awkward and it never restates that one of lei or name is effectively needed despite no required parameters.

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+resource ('verify a company or find its LEI') and enumerates what a lookup yields: legal name, status, legal form, addresses, renewal date, parents, BIC. That lets an agent distinguish it from a screening or batch tool without opening the schema, though it never explicitly contrasts with the singular-vs-batch sibling.

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?

Opens with an explicit trigger ('Use when an agent needs to verify a company or find its LEI'), which is clear context for selection. It does not state when-not to use it or name an alternative for multi-company or sanctions-style checks, so exclusions are absent.

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