mcp-brasilapi

Overview Schema Source Related Servers Discussions Admin

cnpj__buscar

Retrieve corporate registration data for any Brazilian company by providing its CNPJ number. The tool accesses official records from the Receita Federal.

Instructions

Consulta dados cadastrais de uma empresa pelo CNPJ (Receita Federal via Minha Receita).

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

Input Schema

Name	Required	Description	Default
`cnpj`	Yes	CNPJ com 14 dígitos, com ou sem formatação (ex.: "19131243000197").

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 16, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action and source, omitting details like read-only nature, rate limits, error handling, or response format. This is insufficient for a tool with no annotations.

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 sentence directly conveys the tool's purpose without wasted words. It is efficiently front-loaded.

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?

Given the single parameter and presence of an output schema, the description is largely complete for a simple lookup tool. However, it could mention that the tool performs a read-only query, which is implied but not explicit.

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 description adds no extra meaning beyond the schema's parameter description. Baseline 3 applies as per criteria.

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 clearly states the verb 'Consulta' (consult) and resource 'dados cadastrais de uma empresa pelo CNPJ', and specifies the data source. This distinguishes it from sibling tools that handle different entities like banks, CEP, or currencies.

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?

The description implies usage for CNPJ lookups but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. It relies on the tool name and sibling context to differentiate.

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