Skip to main content
Glama

br_business_intel

Brazilian Corporate CNPJ KYB Dossier (QSA partners, Simples/MEI, B2B Risk Score), IBGE Geo-CEP lookup, CPF/CNPJ Mod-11 validator, and Central Bank PIX BRCode (EMVCo + CRC16) generator/decoder (0.01 USDC via x402 on Base).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "br_business_intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
cepNoBrazilian postal code (CEP, 8 digits) to enrich address, IBGE municipality code, state UF, and area code (DDD).
cnpjNoBrazilian corporate tax ID (CNPJ, 14 digits) to fetch full Receita Federal dossier, QSA partners, tax regime (Simples/MEI), and B2B credit/compliance risk score.
aiSummaryNoGenerate an executive B2B compliance summary using Cloudflare Workers AI (default: true).
pixDecodeNoRaw PIX Copy-and-Paste string (000201...) to parse EMV tags and verify CRC16 integrity.
pixGenerateNoGenerate an official Central Bank of Brazil (BCB EMVCo) PIX Copy-and-Paste payload with CRC16-CCITT checksum.
documentToValidateNoCPF (11 digits) or CNPJ (14 digits) to validate mathematical check digits (Mod-11).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 disclosure burden, and it does surface one genuinely important trait: the call costs 0.01 USDC via x402 on Base, which an agent must know before invoking. It says nothing about payment failure behavior, rate limits, latency, or what happens when an invalid CNPJ/CPF is supplied. The default aiSummary=true behavior lives only in the schema, not the description.

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?

It is a single sentence with no filler, so nothing is wasted word-for-word. However, the heavy nested-parenthesis packing of four distinct operations into one run-on makes it hard to parse, and a short structured enumeration of modes would communicate the same content far faster.

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?

There is no output schema, so the description must carry return semantics — and it does reasonably well by naming the dossier fields, IBGE code/UF/DDD, and CRC16 verification. It is still incomplete for a six-parameter, multi-mode, nested-object tool: mode dispatch rules, whether calls are one-shot per mode, and the paid x402 flow are all left under-specified.

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 the schema already documents every parameter including the nested pixGenerate object with its required key, merchantName, and merchantCity. The description restates the same capability set at a high level and adds no syntax, format, or constraint detail beyond it. Baseline 3 is appropriate.

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 four concrete capabilities with specific resources: a CNPJ KYB dossier (QSA partners, Simples/MEI, risk score), IBGE Geo-CEP lookup, a CPF/CNPJ Mod-11 validator, and a PIX BRCode generator/decoder. An agent can tell exactly what domain this covers. It loses a point because the tool is a composite of four unrelated operations presented as one flat sentence, with no statement of which operation is primary.

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?

There is no explicit when-to-use or when-not guidance, and no alternatives are named. The usage model is only implied by the parameter names — cep for geo, cnpj for the dossier, documentToValidate for the validator, pixDecode/pixGenerate for PIX — but with six optional parameters and zero required, the description never states whether exactly one mode parameter should be supplied or whether they can be combined in a single call.

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