Skip to main content
Glama

Fichário — CNPJ Brasil

consultar_cnpj

Ficha completa de uma empresa pelo CNPJ (14 dígitos): razão social, atividade, endereço, porte, telefone, site e Instagram. Limites grátis: 60 req/min e 3.000/dia por IP; Pro (Bearer fch_live_…): 10×. CNDT/publicações: 6/min e 40/dia (Pro 60/400). Base 2026-11. Volume: /precos ou WhatsApp +55 21 99598-8404.

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

Input Schema

NameRequiredDescriptionDefault
cnpjYesCNPJ com ou sem pontuação
verificarNoConferir a situação cadastral ao vivo na Receita (padrão: true). Também acha CNPJs baixados/inaptos fora da base.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / verificar
      Added value: +{
      +  "description": "Conferir a situação cadastral ao vivo na Receita (padrão: true). Também acha CNPJs baixados/inaptos fora da base.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: concrete rate limits (60 req/min, 3.000/day per IP), a distinct tighter quota for CNDT/publicações, the Pro auth scheme (Bearer fch_live_…), and the data vintage (Base 2026-11). It does not say whether the live Receita check in 'verificar' adds latency or fails when the source is unavailable, which is the main remaining gap.

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?

Purpose is front-loaded in the first clause, followed by quota and data-freshness facts in a compact sequence with no filler sentences. The trailing pricing/WhatsApp contact is marginally promotional but still actionable for an agent that needs higher volume.

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 two-parameter, read-only lookup with no output schema and no annotations, the description compensates well by listing the returned fields, the auth model, and the rate limits. Error handling for an invalid or unknown CNPJ is the one thing an agent might still want.

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%, so both parameters are already documented, including the default of 'verificar' and its live-check behavior. The description adds only the '14 dígitos' constraint, which slightly sharpens the schema's 'com ou sem pontuação' note but goes no further.

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 ('Ficha completa de uma empresa pelo CNPJ') and enumerates the returned fields (razão social, atividade, endereço, porte, telefone, site, Instagram), so an agent knows exactly what it gets. It does not differentiate itself from siblings such as buscar_empresa or consultar_lote, which keeps it below 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 '14 dígitos' / single-CNPJ framing signals a one-company lookup as opposed to a batch or advanced search, but no alternative is named and no when-not-to-use condition is given. An agent must infer that consultar_lote handles multiple CNPJs.

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