Skip to main content
Glama

grid402_cnpj

Read-onlyIdempotent

Brazilian Receita Federal CNPJ lookup: registration status, legal name, CNAE and address (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_cnpj"
  }
}

Input Schema

NameRequiredDescriptionDefault
cnpjYes14-digit Brazilian CNPJ number (e.g. 00000000000191).
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. Changed1 schema field changed
    • addedInput schema / properties / cnpj / description
      Added value: +"14-digit Brazilian CNPJ number (e.g. 00000000000191)."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: the upstream data source (Receita Federal) and the cost (0.0200 USDC / 4 credits). It omits failure modes, e.g. what happens with a malformed or unknown CNPJ.

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: resource and returned fields first, price last. Every clause carries information and there is no filler.

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 two-parameter read-only lookup with no output schema, the description's enumeration of returned fields substitutes usefully for the missing return documentation. Pricing and data provenance are covered; only the absence of failure-mode/empty-result notes keeps it short of full completeness.

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 coverage is 100%, and the schema already documents both the 14-digit CNPJ format and the various accepted payment_tx_hash forms. The description adds nothing on parameter semantics, 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 names a concrete action (lookup) and a specific resource (Brazilian Receita Federal CNPJ) and enumerates the returned data (registration status, legal name, CNAE, address). It does not, however, distinguish this from plausible siblings such as grid402_simples or grid402_kyb_audit, which likely touch overlapping company-registry data.

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 explicit when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative for related company-data lookups. The only implicit signal for selection is the per-call price, which doesn't tell an agent when this tool is the right choice.

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