Skip to main content
Glama
radar-cnpj-mcp

radar-cnpj-mcp

by wendersoon

Andamento do download

andamento_download
Read-only

Check the status and current stage of the last initiated CNPJ data download to monitor whether it is downloading, completed, errored, or interrupted.

Instructions

Informa o estado do último download iniciado (baixando, concluido, erro ou interrompido) e a etapa atual.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond them by enumerating the possible return states and noting that the current stage is included, effectively communicating the response shape without an output schema. It omits the edge case of no download ever having been started.

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, front-loaded sentence with zero filler. The parenthetical state list is the highest-value information and is placed prominently rather than buried.

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 no-parameter, no-output-schema read tool, the description carries the burden of telegraphing return values, and it does so by listing the four states plus the current stage. It could be complete with one more clause covering the no-active-download case or polling expectations.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The schema already fully covers the empty input object, and the description correctly spends no words on parameters.

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+resource in a single clause: it reports the state of the last started download and its current stage. The enumerated states (baixando, concluido, erro, interrompido) make the object of the tool concrete. It does not name sibling tools or clarify its relationship to baixar_dados, so it falls short of a 5.

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: the phrase 'último download iniciado' signals that this is meant to be called after baixar_dados, but the description never says so explicitly. There are no exclusions, no mention of polling, and no guidance on when to prefer status_base or other status siblings.

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