Skip to main content
Glama

Latam Validate

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Validate Cnpj

validate_cnpj
Read-onlyIdempotent

Validate a Brazilian CNPJ (Cadastro Nacional da Pessoa Jurídica, the 14-character company tax ID) and look up the company registration: legal name (razão social), trade name, CNAE activity, address, registration status (situação cadastral), and partners (QSA). Checksum supports both the classic numeric format and the alphanumeric CNPJ introduced in 2026. Punctuation (12.345.678/0001-95) is accepted. Set skip_lookup to validate the checksum only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cnpjYesThe CNPJ, e.g. "33.000.167/0001-01" or "33000167000101".
skip_lookupNoIf true, only run the checksum and skip the BrasilAPI company-registration lookup. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "cnpj": "33.000.167/0001-01"
+  },
+  {
+    "cnpj": "33000167000101",
+    "skip_lookup": true
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable context: support for numeric and alphanumeric CNPJ, punctuation acceptance, and the skip_lookup flag behavior. No contradictions.

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?

Three sentences, front-loaded with the primary purpose. Every sentence adds value: validation + lookup, format details, skip_lookup option. No unnecessary words.

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?

The description covers the main functionality and parameters well. No output schema, but the description mentions what data is returned. For a simple validation tool with annotations, this is nearly complete. Minor gap: no mention of error handling or status codes.

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 coverage is 100% and includes detailed descriptions. The description adds minor context (checksum support, punctuation) not present in schema for the cnpj param, but otherwise does not significantly enhance understanding beyond the schema. Baseline 3 is appropriate.

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 clearly states it validates a Brazilian CNPJ and looks up company registration details. It uses specific verbs (validate, look up) and identifies the resource (CNPJ). The sibling tools include validate_cpf and validate_clabe, so the target entity is distinct.

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 description implies when to use (to validate a CNPJ) but does not explicitly compare to siblings or state when not to use. It could mention, for example, that validate_cpf is for individual tax IDs. The guidance is adequate but not explicit.

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

All Latam Validate 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