Skip to main content
Glama

BRAINIAC Equity Analytics

Validate an LEI check digits

equity-analytics_lei-validate
Read-onlyIdempotent

Check ISO 17442 structure and ISO/IEC 7064 MOD 97-10 check digits for a Legal Entity Identifier. Registration status is not looked up. Price $0.01 USDC. POST /api/v1/equity-analytics/lei-validate. An unpaid call returns the x402 payment terms and does not run.

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": "equity-analytics_lei-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiYeslei, string, length 18 to 24. Required.

Output Schema

NameRequiredDescriptionDefault
validNovalid. Boolean.
sourcesNosources. Array.
louPrefixNolouPrefix. String.
checkDigitsNocheckDigits. String.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavior: a $0.01 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing. That payment-gating detail is exactly the kind of context annotations cannot express.

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?

Four short sentences, front-loaded with the core purpose and followed by scope, cost, and transport details. The endpoint path is mildly redundant but each sentence carries operational information; nothing is padded.

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?

An output schema exists, so return values need not be described, and the payment/execution semantics are spelled out. For a one-parameter validation tool this is nearly complete; only the outcome on an invalid LEI is left implicit.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents the lei string and its 18-24 length bounds. The description only restates that it is a Legal Entity Identifier, adding no format, normalization, or example guidance beyond the schema.

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: check ISO 17442 structure and ISO/IEC 7064 MOD 97-10 check digits for an LEI. It also scopes out registration-status lookup, which sharpens the boundary. It does not name the sibling equity-analytics_security-identifier-validate, so the agent must infer the split between identifier validators.

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?

The exclusion 'Registration status is not looked up' tells the agent one thing this tool will not do, which is useful negative guidance. However, there is no positive when-to-use statement and no named alternative for the case where the caller actually wants status or a different identifier type.

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