Skip to main content
Glama

radar-cnpj

by com.radar-cnpj
OverviewDiscussionsAdmin

Check a company (live)

consulta_cnpj
Read-onlyIdempotent

Brazilian company record by CNPJ from the Federal Revenue (Receita Federal), with the special status when there is one (bankruptcy, judicial recovery, liquidation); its sanctions (CEIS, CNEP, CEPIM, leniency agreements, TCU and the CNJ's CNIA, checked live); partners on the politically exposed persons list (CGU); tax status (federal tax debt, installment agreements, tax incentives and construction works); the Federal Revenue chronic tax debtor list (devedorContumaz.consta: barred from public tenders); environmental and labor risk (forced-labor list, Ibama embargoes and fines); government contracts (PNCP, federal contracts since 2013 and sales to municipalities in the state of SP, from TCE-SP) and BNDES financing; registrations with regulators and official registries (CVM, Central Bank, ANS, ANTT, ANP, ANEEL, Anatel, Anvisa, CNES, Cadastur, Ibama, ANAC and SICAF); CVM investment funds; and the address on the map (CNEFE/IBGE). Accepts the numeric and the alphanumeric CNPJ. Personal data in the record comes masked. sancoes has what public registries record against the whole company (the CNPJ root), updated daily: useful to vet suppliers. The daily free allowance is 10 lookups per account, or per network without an account. After that, the operation uses the holder's lookup balance or returns 402 with the available payment options. Read pricing before spending.

Input Schema

NameRequiredDescriptionDefault
cnpjYesCNPJ, with or without punctuation.
temasNoComma-separated topics: dados, socios, sancoes, fiscal, divida, obras, trabalho, ibama, contratos, pep, vendas, campanhas, prefeituras, sicaf, aeronaves, fundos, rntrc, bndes, registros; todos. Omit for the full record. Basic company data always stays. Unrequested blocks are omitted; null means unchecked. Personal data remains masked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / temas
      Added value: +{
+  "description": "Comma-separated topics: dados, socios, sancoes, fiscal, divida, obras, trabalho, ibama, contratos, pep, vendas, campanhas, prefeituras, sicaf, aeronaves, fundos, rntrc, bndes, registros; todos. Omit for the full record. Basic company data always stays. Unrequested blocks are omitted; null means unchecked. Personal data remains masked.",
+  "maxLength": 240,
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / cnpj / description
      Previous value: -"CNPJ, com ou sem pontuação"New value: +"CNPJ, with or without punctuation."
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses the free-allowance quota (10 lookups per day), the 402 failure mode with payment options, that personal data comes back masked, and that live external checks are performed. These are exactly the operational facts an agent needs before calling, though the pricing pointer is deferred rather than stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the bulk is a long run-on catalogue of data blocks that largely duplicates the `temas` enum already documented in the schema. Several listed categories (CVM, ANS, ANTT, ANP, ANEEL…) are pure enumeration and could be compressed without losing decision-relevant information.

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 read-only, open-world lookup with no output schema, the definition covers cost, quota, masking, partial/omitted blocks and null-means-unchecked semantics — enough to call it correctly. The remaining hole is sibling disambiguation among the several CNPJ tools in the set.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds value by noting that both numeric and alphanumeric CNPJ forms are accepted (the schema only mentions punctuation) and by clarifying that `sancoes` reflects records at the CNPJ root, which the enum entry alone does not convey.

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 opening clause states a specific verb and resource: a Brazilian company record fetched by CNPJ from the Receita Federal, then enumerates the covered datasets (sanctions, PEPs, tax status, contracts, regulators). It is unambiguous what the tool returns, but it never contrasts itself with the very similar siblings get_cnpj, dossier_cnpj or consulta_cadastro, so an agent must guess which of them to call.

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: 'useful to vet suppliers' and the note that `sancoes` covers the CNPJ root. There is no explicit when-to-use / when-not-to-use statement and no routing to alternatives such as dossier_cnpj for a full profile or get_cnpj for a bare lookup.

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

All radar-cnpj toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources