Skip to main content
Glama

Grid402 — Brazil Public Data & Network Oracle

grid402_compliance

Read-onlyIdempotent

Compliance 360 risk score (Receita Federal + CGU + corporate history), 0-100 (0.0300 USDC / 6 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_compliance"
  }
}

Input Schema

NameRequiredDescriptionDefault
cnpjYes14-digit Brazilian CNPJ number for 360 compliance scoring.
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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-structured context: the score range (0-100), the upstream registries consulted, and the price (0.0300 USDC / 6 credits), which matters because it is a paid call. It does not say what happens on an invalid CNPJ or whether a cached/partial result is returned.

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 dense sentence with the resource, its sources, its output scale and its cost front-loaded; nothing is padding. The stacked parentheticals make it slightly telegraphic, but it is appropriately sized for a two-parameter tool.

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?

With no output schema, the description must carry return-value context; it gives the 0-100 score scale but not the shape of the underlying registry breakdown or error behavior. For a simple one-required-parameter read tool with full annotation coverage and full schema coverage, this is adequate but leaves a real gap on return format.

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 both cnpj and payment_tx_hash fully documented in the schema, so the baseline is 3. The description contributes nothing further about either parameter (no CNPJ formatting rules or payment-mode behavior beyond what the schema states).

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 a specific output artifact (a 'Compliance 360 risk score' on a 0-100 scale) and enumerates its data sources (Receita Federal, CGU, corporate history), which separates it from narrow siblings like grid402_cnpj or grid402_sanctions. It does not explicitly say how it differs from grid402_kyb_audit, so it stops 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?

There is no when-to-use, when-not-to-use, or alternative-routing language at all. The only implied guidance is that a Brazilian CNPJ is the subject, leaving the agent to infer that this is the broad due-diligence call versus the point-lookup siblings.

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.