Skip to main content
Glama

Returns Brazilian company data from BrasilAPI: legal name

company_br
Read-only

Returns Brazilian company data from BrasilAPI (CNPJ lookup, MIT licence): legal name, trade name, status, opening date, legal nature, CNAE activities, address, share capital, and partners (QSA). CNPJ check digits are validated before any network call. Rate limit: BrasilAPI allows ~3 req/s. Related tools on this server, for a different need: company_fr when you need to search French companies by name or SIREN/SIRET; company_ticker when you need to convert a stock ticker, CIK or company name to the other two. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
cnpjYesCNPJ number — 14 digits, with or without formatting (e.g. 00.000.000/0001-91 or 00000000000191)

Output Schema

NameRequiredDescriptionDefault
cnpjNo
emailNo
phoneNo
sourceNo
statusNo
addressNo
mainCnaeNo
partnersNo
checkedAtNo
legalNameNo
tradeNameNo
disclaimerNo
statusDateNo
legalNatureNo
openingDateNo
shareCapitalNo
secondaryCnaesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses several operational facts an agent needs: CNPJ check digits are validated before any network call, the upstream rate limit is ~3 req/s, calls cost $0.003 via x402, and failed calls are not charged. These are genuine behavioral details not derivable from structured fields.

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 content is dense and front-loaded: capability first, then sibling routing, then cost and rate limits. The payment-network enumeration ("USDC on Base, Solana and 10 more networks") and the MIT licence aside are the least load-bearing clauses, but the overall structure stays tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only lookup with an output schema, this description covers everything an agent needs: what is returned, validation behavior, rate limits, pricing, and failure charging semantics. Listing the returned fields is arguably redundant with the output schema, but it does no harm.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter and the schema fully describes it, including both formatted and raw form examples. The description reinforces that check digits are validated before any network call, so invalids fail locally rather than costing a request.

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?

The description opens with a specific verb and resource — returns Brazilian company data from BrasilAPI via CNPJ lookup — and enumerates the returned fields (legal name, status, CNAE activities, QSA partners), so an agent knows exactly what it gets. It also names the sibling tools it is not, making the scope unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to route elsewhere with explicit conditions: company_fr for French companies by name or SIREN/SIRET, and company_ticker for ticker/CIK/name conversion. Combined with the CNPJ-validation note, an agent can decide between this and adjacent lookups without guessing.

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