Skip to main content
Glama

Sintegra CCC

by io.github.mcp-dir

sintegra_ccc_consultar

Read-onlyIdempotent

Consulta o 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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds valuable context: payment model, public data nature, and LGPD compliance, which goes beyond the structured annotations. 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?

The description is compact and front-loaded with purpose, followed by practical usage details. No redundant sentences; every part adds value.

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 description covers purpose, data sourcing, and legal responsibility, but with no output schema and low parameter coverage, it misses details like the meaning of 'completo', mutual exclusivity of CPF/CNPJ, and expected response structure. These gaps are notable for a query tool.

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?

The description names the main parameters (CPF/CNPJ, inscrição estadual, UF), but schema coverage is 0% and the optional 'completo' parameter is not explained. It also does not clarify whether CPF and CNPJ are mutually exclusive despite schema listing both as required, creating potential ambiguity.

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 queries the CCC (Cadastro Centralizado de Contribuinte) from Sintegra using CPF/CNPJ, inscrição estadual, and UF. It uses a specific verb (Consulta) and resource, distinguishing it from sibling platform tools like authenticate or marketplace.

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?

Provides clear context on when to use: for querying public taxpayer data with prepaid credit and no credentials. It does not explicitly describe exclusions or alternatives, but the intended use case is evident and not misleading.

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

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

The tools are mostly distinct, but connect and toolkit_info both report connection/status information, and authenticate overlaps with connect around authentication flow. The marketplace tool is a catch-all with many sub-actions, but as a named tool it is unique.

Naming Consistency2/5

Naming conventions are mixed: single verbs (authenticate, connect), noun tools (marketplace, toolkit_info), verb_noun in English (report_bug, show_version), and one Portuguese verb_noun (sintegra_ccc_consultar). This inconsistency makes the tool list feel chaotic and hard to predict.

Tool Count2/5

Seven tools is a reasonable number, but the server is named 'Sintegra CCC' and only one tool (sintegra_ccc_consultar) actually provides the core domain capability. The other six are generic MCP.AI platform utilities, making the tool set feel misaligned with the server's stated purpose.

Completeness2/5

For a Sintegra CCC server, the surface is severely lacking: only one consultation tool exists, with no additional domain operations or auxiliary features. While the platform-management tools are complete for their own domain, they do not contribute to the stated Sintegra CCC purpose, leaving the domain coverage nearly empty.

Resources