Skip to main content
Glama
Sign In
grid402-mcp

grid402-mcp

by oliveiratc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

grid402_cnpj

Retrieve public Brazilian company registration data by CNPJ—legal name, status, CNAE, address, and share capital—via a paid lookup.

Instructions

Consulta dados cadastrais públicos de Pessoa Jurídica da Receita Federal (razão social, nome fantasia, situação cadastral, CNAE, endereço e capital social). Requer 0.0020 USDC.

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
cnpjYesNúmero de CNPJ com 14 dígitos com ou sem formatação (ex: "00.000.000/0001-91" ou "00000000000191").
payment_tx_hashNoHash opcional de transação na Base Mainnet com 0.0020 USDC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose meaningful traits: the data is public, sourced from the Receita Federal, and costs 0.0020 USDC. It does not explain the payment flow (whether payment_tx_hash must be supplied, what happens on unpaid or failed calls), rate limits, or error behavior.

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?

Two short sentences with the resource and return fields front-loaded, followed by the cost constraint. The field enumeration is long but earns its place by telling the agent what data comes back, though it could be trimmed slightly.

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 simple two-parameter read tool with no output schema and no annotations, the description covers purpose and returned fields adequately. The main gap is the payment mechanism, since the cost is stated but the consequence of omitting payment_tx_hash is never clarified.

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 both parameters (cnpj format and payment_tx_hash) are already fully documented in the schema. The description adds no further detail on parameter formats or interactions, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (consulta) and a precise resource (dados cadastrais públicos de Pessoa Jurídica da Receita Federal) and enumerates the returned fields (razão social, nome fantasia, situação cadastral, CNAE, endereço, capital social). No sibling tool overlaps with Brazilian company registration lookup, so an agent can route here unambiguously.

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?

Usage is only implied by the resource: query company registration data for a given CNPJ. The one explicit precondition given is the 0.0020 USDC cost, which is useful, but there is no statement of when to prefer this over another tool, when not to call it, or what to do when payment is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools