Skip to main content
Glama

Cnpj Br

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Cnpj Lookup

cnpj_lookup
Read-onlyIdempotent

Look up a Brazilian company in the CNPJ registry (Receita Federal, Brazil's federal tax authority) — the primary KYB / due-diligence check for any Brazil company. Give a 14-digit CNPJ (punctuation ok: "33.683.111/0002-80") and get legal name (razão social), trade name, registration status, opening date, legal nature, main CNAE activity, address, share capital, company size, Simples Nacional / MEI tax-regime flags, and the partner/officer list (QSA) with roles. Example: cnpj_lookup({ cnpj: "33683111000280" })

Input Schema

NameRequiredDescriptionDefault
cnpjYesThe company's CNPJ — 14 digits, with or without punctuation, e.g. "33.683.111/0002-80" or "33683111000280"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "cnpj": "33683111000280"
+  },
+  {
+    "cnpj": "33.683.111/0002-80"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark it as read-only, idempotent, and non-destructive. The description adds valuable behavioral context by enumerating the returned data fields, giving an example invocation, and clarifying that punctuation is accepted in the CNPJ. No contradictions with annotations.

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?

The description is concise, front-loaded with the core purpose, and every sentence adds value. The example is compact and useful, making the description highly scannable without unnecessary fluff.

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?

With a single simple parameter and no output schema, the description compensates well by detailing all output fields, the registry source, and an example. It provides a comprehensive picture of what the tool does and returns, making it complete for the tool's complexity.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds an explicit example call with the exact JSON format and reinforces the input format, going slightly beyond the schema by showing a concrete usage pattern, which helps the agent correctly construct the invocation.

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 explicitly states the tool 'Look up a Brazilian company in the CNPJ registry' with a clear verb and resource. It also lists the exact output fields and distinguishes itself from siblings by focusing specifically on CNPJ lookups, making it the go-to for Brazilian company due diligence.

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

Usage Guidelines4/5

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

The description gives clear context ('primary KYB / due-diligence check for any Brazil company') which implies when to use it. It does not explicitly mention alternatives or when-not-to-use, but the provided context is enough for an agent to select this tool appropriately.

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

All Cnpj Br toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources