Skip to main content
Glama

Sintegra CCC Completa

by io.github.mcp-dir

sintegra_ccc_completa_consultar

Read-onlyIdempotent

Consulta completa do Cadastro Centralizado de Contribuinte (CCC) do Sintegra de uma pessoa ou empresa a partir do CPF ou CNPJ, inscrição estadual e UF. 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
UfYes
ieYes
CpfYes
CnpjYes
completoNo

Schema Changelog

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

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (read-only, idempotent, non-destructive), the description adds that the consultation is paid via prepaid credits, requires no credentials, and operates on public data with LGPD compliance responsibilities. This is useful behavioral context not captured in the annotations.

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 well-structured, starting with the core purpose, then payment model, then data nature, and finally legal note. It is slightly verbose but each sentence carries relevant information with no redundancy.

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?

For a simple query tool with 5 parameters and no output schema, the description covers main inputs, payment, and data sensitivity. However, it lacks explanation of the 'completo' parameter, does not resolve the CPF/CNPJ requiredness contradiction, and does not mention the response format or pagination, leaving some ambiguity for an agent.

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?

The description mentions CPF or CNPJ, state registration, and UF, but omits the optional 'completo' parameter entirely. Moreover, it ambiguously says 'ou' (or) for CPF/CNPJ while the schema requires both fields, creating a significant contradiction that undermines parameter understanding.

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 performs a complete consultation of the Centralized Taxpayer Registry (CCC) of Sintegra using CPF or CNPJ, state registration, and UF. This is a specific verb and resource, and it distinguishes itself from generic sibling platform tools.

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 usage for querying public-access tax registry data, and mentions the paid, no-credentials model. However, it does not explicitly state when to use this tool over alternatives or when not to use it, only that it accesses public data.

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

All Sintegra CCC Completa 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.7/5.0
Disambiguation3/5

Most tools have distinct purposes, but there is potential confusion between the marketplace (which can also run CPF/CNPJ queries by invoking external MCPs) and the dedicated sintegra_ccc_completa_consultar tool. Additionally, connect and toolkit_info both report connection status, which may cause mis-selection.

Naming Consistency2/5

Naming is highly inconsistent: some tools are bare verbs (authenticate, connect), one is a noun (marketplace), others are verb_noun with underscores (report_bug, show_version), and the Sintegra tool is a long domain-specific phrase with the verb at the end. There is no discernible pattern across the set.

Tool Count4/5

At 7 tools, the count is within a reasonable range. However, the server's name implies a Sintegra-focused tool, while most tools are generic platform features; still, each tool appears to have a distinct function and the count is not excessive.

Completeness4/5

The core Sintegra consultation is covered by a single comprehensive query tool. Platform-level tools for authentication, connection status, marketplace access, and version reporting round out the surface. Minor gaps exist, such as no explicit tool for managing or reviewing past consultations, but these are likely handled through the marketplace.

Resources