Skip to main content
Glama

Grid402 — Brazil Public Data & Network Oracle

grid402_kyb_audit

Read-onlyIdempotent

Consolidated Corporate KYB Dossier (CNPJ + OFAC/UN Sanctions + GLEIF LEI) (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": {
      "cnpj": "<cnpj>"
    },
    "name": "grid402_kyb_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiNoOptional 20-char ISO 17442 LEI code.
cnpjYes14-digit Brazilian CNPJ number (e.g. 00000000000191).
nameNoOptional legal entity name for OFAC screening.
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

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond them: the call is metered at 0.0200 USDC / 4 credits, which matters for an agent choosing between this bundle and cheaper single-source tools. It does not describe what happens on a missing CNPJ, partial sanctions match, or LEI mismatch.

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 compact line with the resource and the three constituent sources front-loaded, followed by the price. No filler, though the stacked parentheticals are dense to parse.

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?

This is a composite lookup with no output schema, so the description carries the burden of saying what comes back — whether the response contains per-source sections, match/no-match flags, or a consolidated risk verdict — and it does not. Inputs are fully documented by the schema and safety by annotations, but the return shape and partial-result behavior remain unspecified.

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 the baseline is 3. The description does map its three named sources onto the parameters (CNPJ→cnpj, OFAC screening→name, GLEIF→lei), which slightly clarifies intent, but it says nothing about payment_tx_hash or how the optional fields change the result.

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 the resource (a consolidated corporate KYB dossier) and enumerates the three data sources it fuses (CNPJ, OFAC/UN sanctions, GLEIF LEI), which lets an agent distinguish it from the single-source siblings grid402_cnpj, grid402_ofac, grid402_lei and grid402_sanctions. It lacks an explicit verb ('look up', 'screen'), so the action must be inferred from the noun phrase.

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?

The word 'Consolidated' hints that this bundles the individual lookups, but there is no statement of when to prefer this over calling grid402_cnpj plus grid402_ofac plus grid402_lei, nor any exclusion or prerequisite. The agent must infer the routing decision entirely.

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.