Skip to main content
Glama

Fichário — CNPJ Brasil

consultar_lote

Consulta em massa: até 1.000 CNPJs de uma vez; devolve a mesma lista preenchida com os dados da ficha (razão, fantasia, CNAE, natureza, porte, capital, endereço, município/UF, telefone, site, Simples). MEI/EI com CPF sempre mascarado, site e Instagram ocultos e remoção de contato em /remover (LGPD). Grátis até 1.000 CNPJs/dia por IP. Base 2026-11.

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": {
      "cnpjs": "<cnpjs>"
    },
    "name": "consultar_lote"
  }
}

Input Schema

NameRequiredDescriptionDefault
cnpjsYesLista de CNPJs (14 dígitos, com ou sem pontuação), até 1.000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioral burden and does substantial work: it enumerates the returned fields, discloses LGPD masking (MEI/EI CPF always masked, site and Instagram hidden, contact removal via /remover), states a rate limit (free up to 1.000 CNPJs/day per IP) and a data vintage (Base 2026-11). It stops short of describing failure behavior for malformed or not-found CNPJs.

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?

The essential facts (scope, return shape, limit) are front-loaded in the first clause, with caveats trailing. The sentence is dense and runs long with several parenthetical lists, but no clause is filler.

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 one-parameter batch tool with no output schema, the description covers the return content, privacy behavior, quota, and data freshness, which is what an agent needs to call it safely. Error/partial-result semantics for invalid or unknown CNPJs are the main omission.

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 coverage is 100% and the single parameter is fully documented there (14 digits, punctuation optional, max 1.000). The description only restates the 1.000 cap, adding no format or normalization detail beyond the schema, so the baseline 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?

Opens with a specific verb and resource ('Consulta em massa') plus a hard scope boundary ('até 1.000 CNPJs de uma vez') and states what comes back ('a mesma lista preenchida com os dados da ficha'). It never names a sibling, so the contrast with a single-CNPJ lookup must be inferred from the 'em massa' wording rather than stated outright.

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?

The batch size limit and the free-tier quota imply the bulk use case, but there is no explicit statement of when to prefer this over a single-record lookup, no preconditions, and no exclusions. An agent gets a usable hint of the scenario but no routing rule.

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