Skip to main content
Glama

CADIN Estadual

by io.github.mcp-dir

cadin_estadual_consultar

Read-onlyIdempotent

Situação de um CPF ou CNPJ no Cadastro Informativo de Inadimplência (CADIN) das secretarias estaduais de fazenda, por UF. Hospedado pela plataforma, sem credenciais, pague por consulta com crédito pré-pago. Consulta informação de crédito em bureaus e bases oficiais. O uso exige base legal (ex.: análise de risco solicitada pelo titular ou relação contratual). O cliente é o controlador e responde pela finalidade (LGPD).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
UfYes
CpfYes
CnpjYes
completoNo

Schema Changelog

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

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable behavioral context: no credentials required, pay-per-query with prepaid credit, it consults credit bureaus and official bases, and clarifies LGPD compliance responsibilities. This exceeds the annotations' safety profile.

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?

Three focused sentences front-load the core purpose, then add operational and legal context. Every sentence provides necessary information; no filler.

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?

Despite strong annotations and description, there is no output schema, so the description should describe what the response contains ('situação') but doesn't. It also leaves 'completo' unexplained. For a query tool, knowing the return shape is important.

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 covers 0% of parameter descriptions, so the description must compensate. It clarifies that Cpf/Cnpj and Uf are used ('por UF'), but it doesn't explain the 'completo' parameter. It also says 'um CPF ou CNPJ' while the schema requires both Cpf and Cnpj, potentially confusing. Partial compensation.

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?

Description clearly states the tool checks the situation of a CPF or CNPJ in the CADIN database of state finance secretaries by UF ('Situação de um CPF ou CNPJ no Cadastro Informativo de Inadimplência (CADIN) das secretarias estaduais de fazenda, por UF'). This specific verb+resource distinguishes it from the unrelated sibling tools (authenticate, connect, marketplace, etc.).

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 for use: hosted on platform, no credentials, prepaid credit per query, and requires a legal basis under LGPD. It doesn't explicitly name alternatives but contextualizes when the tool is appropriate; sibling tools are clearly not alternatives.

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

All CADIN Estadual 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

Tools like authenticate, connect, and toolkit_info all relate to connection/auth status, which could cause selection confusion. Meanwhile, marketplace is an extremely broad multi-action tool that overlaps conceptually with install and configure functions, though its description is detailed.

Naming Consistency2/5

Naming is inconsistent: single-word tools (authenticate, connect, marketplace) mix with verb_noun patterns (report_bug, show_version), while cadin_estadual_consultar and toolkit_info do not follow a predictable style. This lack of a consistent convention makes the tool set feel disjointed.

Tool Count4/5

With 7 tools, the count is within the typical well-scoped range. However, the mixture of platform management utilities and a single domain-specific query function makes the overall scope ambiguous, slightly reducing the appropriateness.

Completeness2/5

Given the server name 'CADIN Estadual', the tool surface is severely incomplete—there is only one query function with no support for listing states, bulk queries, or managing query history. If the intent is a platform management server, the marketplace tool covers many operations, but the naming suggests a domain-specific service, leaving major gaps.

Resources