Agent Toolbox

Company Lei

company_lei

Read-only

Full official record of a legal entity by its LEI (Legal Entity Identifier) from GLEIF: legal and other names, registered and head-office addresses, company-register number, legal form, status, founding date, LEI status, and its direct and ultimate parent companies. Costs USD 0.005 per call, paid with x402 (USDC on Base); calls that fail are not charged.

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": {
      "lei": "<lei>"
    },
    "name": "company_lei"
  }
}

Input Schema

Name	Required	Description	Default
`lei`	Yes	20-character LEI, e.g. HWUPKR0MPOU8FGXBT394

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only and non-destructive status, but the description adds things they cannot: a per-call price of USD 0.005, the payment rail (x402, USDC on Base), and the failure-billing policy ('calls that fail are not charged'). What's missing is behavior on invalid or unknown LEIs and any rate limits.

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, purpose and result payload front-loaded, cost/payment second. The field enumeration is dense but each item tells the agent what it will receive from a tool with no output schema.

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 description correctly compensates by listing the return fields, and it discloses the payment requirement an agent must anticipate. Not fully complete: unstated behavior for a malformed or unregistered LEI, and no note on response format or latency.

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% and the single parameter already documents the 20-character format with an example (HWUPKR0MPOU8FGXBT394). The description only restates the acronym expansion, adding nothing beyond the schema, so the baseline 3 applies.

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 ('Full official record of a legal entity') plus the exact key ('by its LEI') and the source (GLEIF), and enumerates the returned fields. It differentiates itself from the search-style siblings only implicitly through the LEI lookup key, without naming company_search or company_us.

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: call this when you already hold a 20-character LEI. The cost line ('USD 0.005 per call') gives a real decision input for a paid tool, but no alternative (e.g. name-based company_search) is named and no when-not condition is given.

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

All Agent Toolbox 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?