Skip to main content
Glama

Grid402 — Brazil Public Data & Network Oracle

grid402_lei

Read-onlyIdempotent

Global Corporate Identity (ISO 17442) via GLEIF across 200+ jurisdictions (0.0200 USDC / 4 credits).

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

Input Schema

NameRequiredDescriptionDefault
leiYes20-character ISO 17442 LEI code (e.g. 5493006MHB84DD0ZWV18).
payment_tx_hashNoOptional txHash on Base Mainnet, Session Pass token (pass_g402_...), EIP-3009 base64 payload, or demo for Sandbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the GLEIF source, 200+ jurisdiction coverage, and a per-call cost of 0.0200 USDC / 4 credits, which is essential for an agent deciding whether to spend. It does not explain how the payment_tx_hash gate works (e.g., what happens when it is omitted).

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?

A single front-loaded sentence carrying identity, standard, provider, coverage, and price with no filler. Nothing can be trimmed without losing information the agent needs.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-required-parameter read tool with full schema coverage and no output schema, the core is adequate. However, it never indicates what a successful response contains (legal name, status, addresses, registration), so an agent cannot anticipate the payload. It also leaves the payment flow behavior undocumented despite the required-optional payment parameter.

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%, with the LEI format and the payment options (txHash, Session Pass, EIP-3009 payload, demo) fully documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline of 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?

Names the resource precisely (Global Corporate Identity / ISO 17442) and the data source (GLEIF) with global scope, which separates it from jurisdiction-specific siblings like grid402_cnpj or grid402_simples. The verb is only implied ('identity via GLEIF') rather than stated as a lookup, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to choose this over grid402_kyb_audit, grid402_compliance, or grid402_ofac, nor any mention of prerequisites or exclusions. The agent must infer that this is a raw LEI record lookup versus an audit/compliance workflow.

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.