Skip to main content
Glama
Sign In

hexadata-tools

by io.github.4robot
OverviewDiscussionsAdmin

Look up LEI (GLEIF)

lookup_lei

Use this when you need the legal entity behind a Legal Entity Identifier, or the LEI of a company by legal name, for KYC, supplier onboarding or counterparty checks in 200+ jurisdictions. Verifies the LEI check digits locally, then queries the GLEIF Golden Copy (CC0) live and returns legal name, other names, jurisdiction, legal and headquarters addresses, entity status, registration status and dates. Name search returns up to maxResults candidates and an optional country filter. Not found is a valid (charged) answer; GLEIF outages return SOURCE_UNAVAILABLE without charge.

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": "lookup_lei"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiNo20-character LEI to look up, e.g. "HWUPKR0MPOU8FGXBT394". Provide either lei or legalName.
itemsNoBatch mode: up to 500 items, each with the same fields as a single call. Omit when validating a single value through the top-level fields.
countryNoOptional ISO 3166-1 alpha-2 filter on the legal address country when searching by legalName, e.g. "US".
legalNameNoLegal name to search for, e.g. "Apple Inc". Provide either lei or legalName.
maxResultsNoMaximum matches returned per legalName search (1–50, default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: local check-digit verification, live GLEIF Golden Copy query, returned fields, name-search limits, and billing/error semantics ('not found is a valid (charged) answer', outages return SOURCE_UNAVAILABLE without charge). This is unusually rich context for an agent deciding whether and how to call the tool.

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?

Dense and front-loaded: use case first, then behavior, then return fields and error/billing semantics. Every sentence carries operational value, with no repetition of schema details.

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, so the description appropriately lists the returned fields and explains error and billing behavior. The only notable omission is batch mode via 'items', which is well documented in the schema but not mentioned in the description, leaving a small gap for an agent considering bulk lookups.

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 the schema already documents every parameter including the batch 'items' mode and the either/or lei/legalName requirement. The description adds useful relationship context for name search, maxResults and country filter, but omits batch mode entirely, so it does not meaningfully exceed the schema baseline.

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 and resource: look up the legal entity behind an LEI, or the LEI of a company by legal name. The bidirectional lookup and GLEIF source are explicit, making it easy to distinguish from validator siblings like validate_tax_id or validate_iban.

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 clear use contexts (KYC, supplier onboarding, counterparty checks) and both lookup directions, plus the country filter for name searches. It does not name alternatives or exclusions, but the sibling tools cover different resources, so the routing need is minimal.

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

All hexadata-tools toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources