Skip to main content
Glama

Simples Nacional

by io.github.mcp-dir

simples_nacional_consultar

Read-onlyIdempotent

Consulta a situação de uma empresa no Simples Nacional a partir do CNPJ, incluindo opção e enquadramento. Hospedado pela plataforma, sem credenciais, pague por consulta com crédito pré-pago. Consulta informação de ACESSO PÚBLICO em bases e fontes oficiais (a mesma disponível ao cidadão), não é dado privado nem sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
CnpjYes
completoNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and idempotentHint=true, so the tool is known to be safe. The description adds context about authentication (none), prepaid pricing, and LGPD compliance, which are not in annotations. No contradiction found.

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 three sentences, front-loading the main purpose. It includes necessary usage and compliance details without excessive fluff, though the LGPD sentence is somewhat extra but still concise.

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

Completeness3/5

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

The tool is simple with only 2 parameters and no output schema, yet the description omits explanation of the 'completo' parameter and the return format. It covers payment, auth, and data type, but gaps remain.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only implicitly references the CNPJ parameter ('a partir do CNPJ'). The 'completo' boolean parameter is not explained at all, leaving the agent to guess its purpose.

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 the tool consults a company's Simples Nacional status from CNPJ, including option and enquadramento. This specifies a concrete action and resource, and the sibling tools (authenticate, connect, etc.) are unrelated, so there's no confusion.

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?

It provides context for when to use: hosted platform, no credentials required, pay per consultation with prepaid credit, and public access data. However, it does not explicitly mention alternatives or when not to use, though none of the sibling tools are direct alternatives.

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

All Simples Nacional toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools overlap: connect and toolkit_info both report connection status, and marketplace also lists installed tools. authenticate and connect both handle login/credentials, making it difficult to choose the right tool for a given authentication task.

Naming Consistency2/5

The tool names mix verb-based (authenticate, connect, report_bug), noun-based (marketplace, toolkit_info), and a Portuguese compound (simples_nacional_consultar). There is no consistent naming pattern or language convention across the set.

Tool Count3/5

Seven tools is a reasonable number, but several serve overlapping platform-management purposes (connect, toolkit_info, marketplace) and only one tool relates to the nominal domain of Simples Nacional. The count is acceptable, but the set feels padded with utilities that could be consolidated.

Completeness2/5

The server's main purpose, consulting Simples Nacional, is covered by a single tool with only one operation (simples_nacional_consultar). There is no broader domain coverage (e.g., batch queries, tax statements, or other company data), and the remaining tools are generic platform utilities that don't fill that gap.

Resources