mcp-server-brasil

Overview Schema Source Related Servers Discussions Admin

Consultar CNPJ

consultar_cnpj

Read-onlyIdempotent

Retrieves Brazilian company registration data from Receita Federal using a CNPJ, helping you validate and look up public business records.

Instructions

Dados cadastrais públicos de uma empresa na Receita Federal a partir do CNPJ.

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": "consultar_cnpj"
  }
}

Input Schema

Name	Required	Description	Default
`cnpj`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds meaningful provenance by identifying the Receita Federal as the source of public record data, but it says nothing about invalid or malformed CNPJ handling, whether results are live or cached, or what a missing company returns.

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 front-loaded sentence naming the resource, the source, and the lookup key with no filler. It is appropriately short, though the brevity is part of why format and usage details are absent.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. What remains missing for a lookup tool is input format guidance and error behavior on invalid CNPJs, which the description leaves to the caller to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single cnpj parameter, so the schema contributes only the name and string type. The description mentions the CNPJ as the lookup key but does not state the expected format (14 digits, punctuation allowed or not), which is the main ambiguity for this input.

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?

States a specific verb (consultar) and resource (dados cadastrais de uma empresa), plus the data source (Receita Federal) and the key input (CNPJ). An agent knows exactly what the tool returns, though it does not distinguish itself from the sibling validar_documento, which could plausibly accept the same CNPJ.

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 description gives no when-to-use guidance, no exclusions, and does not name an alternative such as validar_documento for validation-only needs. Usage is only inferrable from the stated purpose.

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

Deploy Server