Skip to main content
Glama
Sign In
radar-cnpj-mcp

radar-cnpj-mcp

by wendersoon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Baixar dados da Receita

baixar_dados
Destructive

Download Receita Federal CNPJ files and rebuild the local database in the background for selected Brazilian states or the whole country, replacing the current base when complete.

Instructions

Baixa os arquivos da Receita Federal e monta a base local, em segundo plano. São cerca de 7 GB de download, mesmo para uma só UF, e são necessários cerca de 20 GB livres durante o processo, que costuma levar mais de meia hora. SUBSTITUI a base atual quando termina: informe todas as UFs desejadas, inclusive as já importadas. Só use depois que o usuário confirmar as UFs e o download. Acompanhe com andamento_download; a base atual continua disponível até o fim.

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

Input Schema

NameRequiredDescriptionDefault
mesNoMês de referência (AAAA-MM). Padrão: o mais recente.
ufsNoUFs a importar. Informe ufs ou todas.
todasNoImportar o Brasil inteiro.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (destructive, openWorld, non-idempotent), the description discloses concrete costs (7 GB download, 20 GB free disk, 30+ minutes), the destructive scope ('SUBSTITUI a base atual quando termina'), and the mitigating behavior that the current base remains available until completion.

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?

It is front-loaded with the download and disk-cost warning, then the replacement constraint, then the confirmation prerequisite and monitoring pointer. Every sentence carries operational weight with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a long-running destructive mutation with no output schema, the definition covers duration, resource requirements, replacement semantics, confirmation gating, and monitoring, which is everything an agent needs to invoke it safely.

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 parameters are already documented, but the description adds meaning the schema lacks: that 'ufs' must include already-imported UFs because the base is replaced wholesale. It does not further explain 'mes' or 'todas', leaving those to the schema.

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 gives a specific verb and resource ('Baixa os arquivos da Receita Federal e monta a base local') plus execution mode ('em segundo plano'), which clearly distinguishes it from siblings like exportar_csv and status_base.

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

Usage Guidelines5/5

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

It states an explicit prerequisite ('Só use depois que o usuário confirmar as UFs e o download') and names the companion tool for monitoring ('Acompanhe com andamento_download'), so the agent knows both when to call it and what to do next.

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