Skip to main content
Glama

Fichário — CNPJ Brasil

dados_cvm

Se o CNPJ é (ou foi) companhia aberta na CVM: selo 'Companhia aberta (CVM)', código CVM, situação do registro (ATIVO, CANCELADA, SUSPENSO) e datas, tickers, receita líquida e lucro líquido da última DFP (exercício) e do último ITR (acumulado no ano) com fonte e data de referência, e cotação semanal B3 (COTAHIST). Fonte: dados.cvm.gov.br. Limites grátis normais.

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

Input Schema

NameRequiredDescriptionDefault
cnpjYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: coverage is conditional on CVM registration status, the data source is dados.cvm.gov.br, each figure carries its own source and reference date, and free-tier limits apply. It omits equally relevant behavior, such as what is returned for a CNPJ that was never an open company (empty result vs. error), whether the call costs quota, and whether results are cached, so the disclosure is partial.

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 scope condition is correctly front-loaded, but the core content is one very long run-on sentence that packs registry fields, financial fields, quotes, source, and limits together without separators. Every clause is informative, yet the flat enumeration makes it slower to scan than a short bulleted field list would.

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?

With no output schema and no annotations, the description does the right thing by enumerating the returned fields and their provenance, which partly substitutes for the missing output schema. However, for a single-parameter lookup tool it still leaves the CNPJ input format and the empty/error case undefined, so an agent cannot fully predict the call contract.

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

Parameters2/5

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

There is one parameter, cnpj, and the input schema gives it no description at all (0% coverage), so the description must compensate. It qualifies which CNPJ is meaningful (one that is or was a CVM-registered open company) but says nothing about expected format: digits only or masked, length, or whether a parent/group CNPJ is accepted.

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 description names a specific resource (CVM open-company registry data for a CNPJ) and enumerates concrete returned fields: seal, CVM code, registration status values (ATIVO, CANCELADA, SUSPENSO), tickers, DFP/ITR financials, and B3 COTAHIST quotes. It is clear what the tool returns, but it never distinguishes itself from overlapping siblings such as consultar_cnpj or dados_bolsa, even though it also returns quote data.

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 through the scope condition: it applies when the CNPJ is or was a publicly traded company registered with CVM, which implicitly tells the agent when to expect data back. There is no explicit when-to-use, no when-not, and no named alternative for plain company lookups or pure market quotes, so the agent must infer routing from sibling names alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources