Skip to main content
Glama
Sign In

x402-solana

by io.github.digitalweb33333-creator
OverviewDiscussionsAdmin

gleif_lei

Look up any Legal Entity Identifier (LEI) for company information lookup and counterparty / know-your-business (KYB) identity against the official GLEIF global registry — returns legal name, status, jurisdiction, legal form and registered address, real-time, worldwide coverage. Price: $0.01 per call (x402 payment, USDC on Base mainnet).

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

Input Schema

NameRequiredDescriptionDefault
leiYes20-character LEI, e.g. '529900T8BM49AURSDO55'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the output fields, real-time nature, worldwide coverage, and pricing/payment details ($0.01 per call via x402). It does not mention failure modes or status codes, but for a lookup tool the disclosed context is substantial.

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?

The description is two sentences, front-loaded with purpose, then returns and pricing. Every clause adds value—no filler or redundancy.

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?

Despite lacking an output schema, the description enumerates the key return fields (legal name, status, jurisdiction, legal form, registered address) and adds real-time/coverage/price context. For a single-parameter lookup, this is sufficient for an agent to understand expected behavior.

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 the 'lei' parameter already described (20-character format and example). The tool description adds no extra parameter-level nuance beyond restating that it looks up an LEI, so it meets the baseline without exceeding 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?

The description clearly states the verb ('Look up') and the specific resource ('Legal Entity Identifier (LEI)') against the official GLEIF registry. It lists the returned fields (legal name, status, jurisdiction, etc.) and explicitly positions it for KYB/company lookup, which distinguishes it from siblings focused on crypto/trading/sanctions.

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?

The description provides a clear context for use: 'for company information lookup and counterparty / know-your-business (KYB) identity.' It does not explicitly name alternatives or exclusions, but the sibling tools are thematically different, making the intended use unambiguous.

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

All x402-solana toolsInspect
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