Skip to main content
Glama

Fichário — CNPJ Brasil

dados_bolsa

Se a empresa é companhia aberta na B3: tickers, cotação, valor de mercado, P/L e P/VP (Genesis Bolsa, CVM + B3). 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": "dados_bolsa"
  }
}

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 does real work: it discloses data provenance, tiered rate limits (60/min, 3.000/day free; 10× Pro with Bearer fch_live_), separate CNDT/publicações quotas, and a base date of 2026-11. It does not say what happens when the company is not listed (error vs. empty result) or what authentication is required beyond the Pro token, which matters for a data-lookup tool with no annotations.

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 text is dense but front-loaded with a conditional rather than the core action, and it mixes operational facts (rate limits, base date) with vendor/marketing content (WhatsApp number, /precos endpoint) that does not help an agent invoke this tool. The quota details earn their place; the contact channel does not.

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?

For a one-parameter lookup with no output schema and no annotations, the definition covers operational context (quotas, provenance, data vintage) well but omits the two things most needed to call it correctly: what the cnpj input expects and how unlisted companies are handled. Adequate but with clear gaps.

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 a single required parameter, cnpj, with 0% schema description coverage, and the description never mentions the parameter or its format (14 digits, punctuation allowed, etc.). The phrase 'Se a empresa…' hints that a company identifier is expected, but an agent gets no confirmation that the input is a CNPJ or how to normalize it, so the description fails to compensate for the coverage gap.

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 and field set — tickers, cotação, valor de mercado, P/L, P/VP — for companies that are companhias abertas on B3, sourced from Genesis Bolsa/CVM+B3. An agent can tell this returns market/equity data rather than, say, CVM filings or sanctions. It loses a point because the leading conditional ('Se a empresa é companhia aberta na B3') frames a condition instead of stating the action directly.

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 conditional clause implies when the tool applies (only for B3-listed companies), which is useful scoping. However, it never names an alternative for non-listed companies or for related needs (e.g., dados_cvm for filings), and offers no explicit 'do not use when' guidance, leaving the agent to infer routing.

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