Skip to main content
Glama
Sign In

WABRA — WhatsApp Business for Brazil

by io.github.Amigov2
OverviewDiscussionsAdmin

Enriquecer CNPJ

enrich_cnpj

Enriquece um CNPJ brasileiro com razão social, endereço, situação cadastral, CNAE, sócios e capital social. Fonte: base RFB.

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

Input Schema

NameRequiredDescriptionDefault
cnpjYesCNPJ no formato XX.XXX.XXX/XXXX-XX ou apenas 14 dígitos

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the returned data fields and the source database (base RFB), which is useful provenance, but it does not state whether the operation is read-only, whether it writes to any system, what permissions are required, or any rate limits. This leaves key behavioral traits unspecified.

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?

Two concise sentences, front-loaded with the purpose and output fields, then the source. No wasted words or filler. Structure is appropriate for the tool's simplicity.

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?

For a single-parameter enrichment tool with no output schema, the description provides the essential return fields and source, which compensates for the missing output schema. However, it omits usage context and operational behavior (e.g., read-only status), leaving some gaps. Given the low complexity and complete schema, it is largely complete but not fully.

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 single 'cnpj' parameter is fully documented in the schema, including accepted formats. The description adds no parameter-level detail beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb ('Enriquece') and resource ('um CNPJ brasileiro') and lists the exact fields returned (razão social, endereço, situação cadastral, CNAE, sócios, capital social). It also names the data source (base RFB). This clearly distinguishes it from the messaging and contact siblings, none of which overlap.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance is given; it only states the function. There are no similar sibling tools to route between, but the description does not tell the agent under what circumstances to prefer this enrichment tool. Usage is only implied by the tool name and purpose.

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

All WABRA — WhatsApp Business for Brazil 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