Skip to main content
Glama

Company lei batch

company_lei_batch
Read-onlyIdempotent

Use when you need to refresh or screen many companies by LEI (KYB, vendor or counterparty lists): up to 200 LEIs in one POST, read from GLEIF in one call: legal name, status, addresses. Returns the paid x402 request for your input (POST /company/lei/batch, $0.02 per call; schema linked). POST that JSON body to the URL with an x402 or MPP client to get the data. Bad input is refused before any charge.

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": {
      "leis": "<leis>"
    },
    "name": "company_lei_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
leisYes1 to 200 LEIs; duplicates are removed

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?

Discloses a non-obvious two-step protocol that annotations cannot convey: the call returns a paid x402 request body (POST /company/lei/batch, $0.02 per call) that must be posted with an x402 or MPP client to obtain data. It also states that bad input is refused before any charge, which resolves the main safety worry for an agent about to spend money. Nothing here contradicts readOnlyHint, idempotentHint or destructiveHint=false.

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?

The usage trigger is front-loaded and every clause carries information about cost, endpoint or data. The mid-sentence colon chains make it dense and slightly hard to parse, but no sentence is filler.

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

Completeness5/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 still names the returned fields and, more importantly, explains that the tool yields a request to be posted rather than the data itself. That covers the one fact an agent would otherwise get wrong.

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% with a single documented parameter, so the schema already carries the semantics. The description restates the 200-item ceiling and dedup behaviour that the schema already declares, adding no format or validation detail beyond it.

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 ('refresh or screen many companies by LEI'), the batch scope ('up to 200 LEIs in one POST'), the data source (GLEIF) and the returned fields (legal name, status, addresses). This clearly separates it from the singular company_lei sibling without naming it.

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 an explicit trigger ('Use when you need to refresh or screen many companies ... KYB, vendor or counterparty lists') that maps to real agent tasks. It stops short of naming when to fall back to the single-LEI tool or what to do for lists over 200, so exclusions are left to inference.

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