Skip to main content
Glama
radar-cnpj-mcp

radar-cnpj-mcp

by wendersoon

Detalhar empresa

detalhar_empresa
Read-only

Get establishment details by CNPJ, including secondary activities, and optionally hide MEI phone and email when sharing results.

Instructions

Mostra todos os dados de um estabelecimento pelo CNPJ, incluindo atividades secundárias.

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

Input Schema

NameRequiredDescriptionDefault
cnpjYesCNPJ com ou sem pontuação.
ocultar_contatos_meiNoOcultar telefone e e-mail de MEIs, que costumam ser os da própria pessoa física. Use ao compartilhar os resultados.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered elsewhere. The description adds that secondary activities are part of the payload, but does not say what happens with an invalid or unknown CNPJ, how large the response is, or that contatos may be suppressed by default.

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 with no filler, and the CNPJ lookup key appears immediately. Its brevity is close to under-specification rather than wordiness, which is penalised elsewhere rather than here.

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 lookup this is close to adequate, and the annotations carry the read-only profile. However, with no output schema the description should say more about what 'todos os dados' returns and any failure mode for an unknown CNPJ.

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% and both parameters are well documented in the schema, including the sharing guidance for ocultar_contatos_mei. The description adds nothing about parameter format or interaction, so the schema baseline of 3 applies.

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 and resource: retrieves all data for a single establishment keyed by CNPJ, and adds the scope detail that secondary activities are included. It does not name the sibling it differs from (buscar_empresas, a search rather than a single-record lookup), so differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'pelo CNPJ' phrasing makes the precondition clear - the agent must already have one CNPJ - which naturally contrasts with the search siblings. There is no explicit when-not guidance, such as what to use for multiple companies or for aggregate counts, so a 4 rather than a 5.

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