mcp-brasilapi

by silasrm

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

corretoras__buscar

Search for a brokerage firm by CNPJ in CVM (Brazilian Securities Commission) records.

Instructions

Busca uma corretora pelo CNPJ nos arquivos da CVM.

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

Input Schema

Name	Required	Description	Default
`cnpj`	Yes	CNPJ da corretora (14 dígitos, com ou sem formatação).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 16, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations provided. Description clearly states it searches by CNPJ, which is the core behavior. No contradictions. Could mention error handling for invalid CNPJ, but acceptable for a simple lookup.

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?

Single sentence, no extraneous content. Front-loaded with key information.

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?

Simple tool with one parameter and output schema, so description is mostly sufficient. Could mention that CNPJ must be 14 digits (already in schema) or behavior on not found, but not critical.

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 describes 'cnpj' with format details; description adds no additional meaning beyond that. Schema coverage 100% sets baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the verb ('Busca'), resource ('corretora'), and search key ('pelo CNPJ') with source ('nos arquivos da CVM'). Distinguishes from sibling 'corretoras__listar' which likely lists all.

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?

Implied usage: use when you have a CNPJ. No explicit when-not or alternatives mentioned, but the sibling tool list provides some context.

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