Skip to main content
Glama

CEIS (Inidôneas e Suspensas)

by io.github.mcp-dir

ceis_consultar

Read-onlyIdempotent

Verifica se uma pessoa ou empresa consta no Cadastro de Empresas Inidôneas e Suspensas (CEIS) a partir do CPF ou CNPJ. 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
CpfYes
CnpjYes
completoNo

Schema Changelog

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

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already specify read-only and idempotent hints; the description adds significant context: data is public, no credentials required, payment model, and LGPD compliance responsibilities. No contradiction with annotations.

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 three focused sentences, front-loaded with purpose, and every sentence adds meaningful information without repetition.

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, but the description omits return format and leaves the required-field ambiguity unresolved. Given the low parameter documentation, it should provide more detail on usage and parameters.

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%, so the description carries the burden. It mentions CPF/CNPJ but does not explain the 'completo' parameter and creates ambiguity by implying either/or when the schema requires both fields. This is a notable gap.

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's function with a specific verb ('Verifica') and resource ('CEIS'), and it is distinct from the generic sibling tools.

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?

The description provides clear context (no credentials, pay-per-query, public data) but does not explicitly mention when-not-to-use or alternatives. Since siblings are unrelated, the context is sufficient.

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

All CEIS (Inidôneas e Suspensas) 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.8/5.0
Disambiguation5/5

Each tool serves a distinct function: authentication, connection status, marketplace operations, bug reporting, version info, toolkit state, and the CEIS lookup. There is minimal overlap, and descriptions are clear enough to prevent misselection.

Naming Consistency2/5

Tool names follow inconsistent patterns: some are bare verbs (authenticate, connect), some are verb_noun (report_bug, show_version), some are nouns (marketplace, toolkit_info), and one is a Portuguese noun-verb combination (ceis_consultar). This mixed convention and language creates a lack of predictable naming.

Tool Count3/5

The count of 7 tools is within the typical range, but the server is named after a specific domain (CEIS) and only one tool relates to it. The other six are generic platform tools, making the scope feel unfocused and the count somewhat inappropriate for the apparent purpose.

Completeness3/5

For the CEIS domain, a single lookup tool covers the likely need (query registrant status). However, the server also includes unrelated platform management tools, and there are no other CEIS-related operations (e.g., history, details, bulk checks), so the surface is thin and not fully developed for the stated domain.

Resources