Skip to main content
Glama

Search LEI by company name

search_lei_by_company_name
Read-onlyIdempotent

Searches the global LEI register by legal entity name. Returns matching entities with their LEI, country and a link to the entity's GlobalFinReg lookup page.

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": {
      "query": "<query>"
    },
    "name": "search_lei_by_company_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results, 1 to 50.
queryYesThe legal name (or part of it) of the entity, at least 3 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description adds value by naming the returned fields (LEI, country, GlobalFinReg lookup link), which annotations do not convey; it omits anything about result ordering or partial-match behavior.

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 tight sentences with zero filler: the first states the action and scope, the second states the return contents. Nothing is buried or redundant.

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 usefully compensates by enumerating the returned fields, and the input contract is fully covered by the schema. It omits pagination/truncation behavior when more than 'limit' entities match, which is the only notable gap for a search tool.

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% - both 'query' (3-character minimum) and 'limit' (1-50, default 10) are fully documented in the schema. The description adds no syntax or format detail beyond what the schema already provides, so 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 and resource ('Searches the global LEI register by legal entity name'), which is far more informative than the title alone. It is distinguishable from siblings like get_lei_record by the name-based lookup, though it never explicitly contrasts itself with them.

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 only implied: an agent can infer you call this when you have a company name and want its LEI. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as get_lei_record for lookups by an already-known LEI.

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