Skip to main content
Glama

Grid402 — Brazil Public Data & Network Oracle

grid402_sanctions

Read-onlyIdempotent

Brazilian CGU CEIS/CNEP administrative sanctions lookup by CNPJ (0.0100 USDC / 2 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_sanctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
cnpjYes14-digit Brazilian CNPJ number to check against CEIS/CNEP.
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.6/5.0
Behavior3/5

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

The annotations already declare this is a safe, read-only, idempotent, open-world query. Beyond that, the description adds genuinely useful cost information (0.0100 USDC / 2 credits), which is the main non-annotation behavior disclosed. It says nothing about what the response looks like, what constitutes a hit, data freshness, or coverage caveats within CEIS versus CNEP.

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?

One tight sentence, front-loaded with the data source and scope, ending with the price. No filler and nothing buried.

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?

For a single-parameter lookup with full schema coverage and strong annotations, the definition is largely sufficient. The notable gap is that no output schema exists, so the description should say what a sanctions match result contains (record list versus boolean), which is the remaining unknown an agent faces.

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%, and the schema already documents the 14-digit CNPJ format and the payment_tx_hash options (Base Mainnet txHash, session pass, EIP-3009 payload, demo). The description only repeats that lookup is 'by CNPJ', adding 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 gives a specific verb+resource+scope: a CEIS/CNEP administrative sanctions lookup restricted to a Brazilian CNPJ and to the CGU data source. That is enough to separate it from a generic corporate-registry lookup, though it never names the sibling tools it should be chosen over (e.g. grid402_ofac or grid402_cnpj).

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternatives; the agent must infer from the scope words 'Brazilian', 'CEIS/CNEP' and 'administrative sanctions' that this is the Brazil-specific sanctions check rather than the global OFAC check. Usage is implied by the resource description, not 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.