Skip to main content
Glama

Antigravity x402 & MCP Gateway

verify_gleif_lei_entity

[0.005000 USDC via x402] Verifies corporate counterparties via the official GLEIF Global LEI Index by legal entity name or 20-char LEI code, returning active/lapsed registration status, legal jurisdiction, headquarters, and BIC mappings.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matching LEI entity records to return (1 to 10, default 3).
queryYesCompany legal name (e.g., 'Apple Inc.', 'BlackRock') or exact 20-character alphanumeric LEI code.
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.005000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It does disclose the commercial mechanic (0.005000 USDC via x402) and the returned fields (active/lapsed status, jurisdiction, HQ, BIC mappings), which is useful beyond the schema. However, it is silent on behavior when no match is found, how lapsed vs. active records are distinguished, and any rate/error characteristics of the paid endpoint.

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?

A single dense sentence with the price/payment model bracketed up front and the core purpose immediately after, leaving no filler. Slightly compressed for the amount of information packed in, but nothing is wasted.

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?

Given no output schema, the description helpfully enumerates the returned data, and the x402 payment requirement is surfaced both in the description and the schema. For a simple three-parameter read tool this is close to complete; only no-match and error behavior remain unexplained.

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 description coverage is 100%, so all three parameters are already documented, including the 20-character LEI format, limit range, and x402 signature semantics. The description only restates the two query modes already present in the schema and adds no new parameter-level meaning, 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?

The description names a specific verb (verifies) and resource (corporate counterparties in the official GLEIF Global LEI Index), plus the two accepted identifier forms. It is unambiguous what the tool does, though it never explicitly contrasts itself with adjacent verification tools such as screen_ofac_sanctions or verify_b2b_email_deliverability.

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?

"Verifies corporate counterparties" implies a use case (counterparty/KYB checks), but there is no statement of when to prefer this over sibling verification tools, nor any exclusions (e.g., sanctions screening is a different tool). Usage is inferable rather than stated.

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.