Skip to main content
Glama
Brazil CNPJ Company Data MCP Server

Brazil CNPJ Company Data MCP Server

Look up Brazilian companies by CNPJ

lookup_brazil_cnpj
Read-onlyIdempotent

Retrieve Brazilian company registry details by CNPJ: legal and trade name, status, size, capital, CNAE activities, address, contacts, Simples/MEI and tax regime, plus optional partner records.

Instructions

Look up Brazilian companies by CNPJ in the Receita Federal open data. Returns one row per company with legal and trade name, registration status, legal nature, size, share capital, main and secondary CNAE activities, address, phones, email, Simples and MEI options, and tax regime; with partners on, one row per partner or administrator (QSA).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lookup_brazil_cnpj"
  }
}

Input Schema

NameRequiredDescriptionDefault
cnpjsNoCNPJs to look up, 14 digits with or without punctuation (07.526.557/0001-00 or 07526557000100). An 8 digit root reads the head office. Up to 10,000 per run. In Clay, put the column inside a one item list.
dedupeNotrue (default) reads a CNPJ once per run even when it appears twice. The repeat is not charged.
max_charge_usdNoOptional. The run stops before a charge that would pass this amount. Summary rows are always returned.
include_partnersNotrue adds one row per partner or administrator (QSA), charged per partner. Default false.
max_partners_per_companyNoMost partner rows per company, 1 to 1000. Default 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds real value by disclosing result granularity (one row per company, or one row per partner when partners are enabled) and naming the QSA field, but it says nothing about cost, rate limits, batch failure behavior, or what happens when a CNPJ isn't found — all relevant for a paid batch lookup.

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?

Front-loaded with the operation and source in the first clause, then the return shape. The long field enumeration in sentence two is dense but earns its place because no output schema exists; it is tight overall, with only mild list-like sprawl.

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 five-parameter batch lookup with no output schema, the description supplies the return entity and its key fields, and the schema covers cost caps and formats. The main remaining gap is the absence of pricing or partial-failure behavior for large batches, which matters here because charging is per partner.

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 each parameter documented including digit formats, the 8-digit root shortcut, batch limits, dedupe charging, and the spend cap. The description adds little beyond echoing include_partners and the QSA row shape, so the schema carries the parameter semantics.

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?

States a specific verb and resource ('Look up Brazilian companies by CNPJ') plus the source dataset (Receita Federal open data), then describes the returned entity shape. An agent knows exactly what it retrieves rather than only the operation name.

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 implied by the output description ('with partners on, one row per partner'), but there is no explicit when-to-use/when-not guidance, no stated prerequisites, and no alternatives. With no sibling tools, the omission is less costly, but the description still doesn't route an agent between configurations.

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