Skip to main content
Glama
orionlabsai

AGENTUM MCP Server

Inteligência empresarial (CNPJ completo)

business_intelligence

Provides Brazilian business intelligence from official data, including registration status, address, partners, and an AI-generated summary. Charges $0.05 USDC per call.

Instructions

Inteligência empresarial brasileira completa: situação cadastral, endereço, atividades, sócios (CPF sempre mascarado pela própria Receita Federal) e resumo gerado por IA a partir só de dados oficiais. Pagamento real de $0.05 em USDC (Base mainnet).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cnpjYesCNPJ brasileiro, 14 dígitos, com ou sem pontuação

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

The description discloses important behavioral aspects: it is a paid operation (real payment of $0.05), CPF data is masked by Receita Federal, and the summary is generated from official data only. However, it does not explicitly state whether the operation is read-only, nor does it mention rate limits or other side effects.

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 description is reasonably concise and front-loaded with the main purpose, followed by the key data points and the payment notice. The payment detail is relevant and not extraneous, though the sentence could be slightly streamlined.

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?

Given the simple input and no output schema, the description adequately covers what the tool returns and the cost implication. It does not specify the output format, but this is not critical for a tool that returns a summary of business data.

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?

The only parameter, cnpj, is fully described in the schema with details on format and punctuation flexibility. The description adds no further meaning beyond the schema, but the schema itself is clear enough for correct usage.

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 clearly states that the tool provides comprehensive Brazilian business intelligence, including registration status, address, activities, partners, and an AI-generated summary. It distinguishes itself by emphasizing the completeness and official data source, though it lacks an explicit verb indicating the action performed.

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?

The description mentions a real payment of $0.05 in USDC, implying a cost consideration, but does not provide explicit guidance on when to use this tool versus the sibling tools like verificar_cnpj or validar_cpf. No conditions or prerequisites are stated.

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