Skip to main content
Glama

CADE: Processos

by io.github.mcp-dir

cade_processos_consultar

Read-onlyIdempotent

CADE: Processos, consulta em fonte oficial. Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta com crédito pré-pago. Consulta informação de fontes e órgãos oficiais brasileiros (a mesma disponível ao cidadão), não é dado sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
paginaNo
processoNo
tipo_pesquisaNo
interessado_remetenteNo

Schema Changelog

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

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety. The description adds valuable behavioral context beyond annotations: payment model (prepaid credit), legal data control (LGPD), and confirmation that data is not confidential. This enriches the agent's understanding without contradiction.

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 a single compact paragraph, conveying all essential context without redundancy. While it includes legal disclaimers (LGPD), these are relevant to data handling and are not excessive. It is well-structured and front-loaded with the core purpose.

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

Completeness2/5

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

With five undocumented parameters and no output schema, the description must compensate by explaining input/output behavior, pagination, or result format. It fails to do so, leaving significant gaps for an AI agent. The legal and payment context is helpful but does not address the operational details needed for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not explain any of the five parameters (query, pagina, processo, tipo_pesquisa, interessado_remetente). With a high parameter count and no documentation, the agent has no guidance on required formats, semantics, or relationships, making this dimension critically deficient.

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 CADE processes from official Brazilian sources, using a specific verb ('consulta') and resource ('Processos'). It distinguishes itself from sibling utilities by specifying the domain and official nature, leaving no ambiguity about its function.

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 for use: it queries official data, requires prepaid credit, and does not need platform credentials. However, it does not explicitly mention when to avoid this tool or suggest alternatives, though the sibling list (authenticate, marketplace, etc.) makes its niche apparent. No exclusions are stated, so it falls short of a 5.

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

All CADE: Processos 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
Disambiguation4/5

Most tools have distinct purposes, but 'authenticate' and 'connect' both involve authentication flows, and 'toolkit_info' overlaps slightly with 'connect' regarding status. The descriptions are detailed enough to differentiate them, but the boundary between these administrative tools could lead to some mis-selection.

Naming Consistency3/5

Names use consistent snake_case, but conventions vary: some are verbs (authenticate, connect, report_bug, show_version) while others are nouns (marketplace, toolkit_info). The domain-specific 'cade_processos_consultar' breaks the pattern by mixing a proper noun with a verb. Overall, the mixture is readable but not uniform.

Tool Count4/5

Seven tools is within the ideal range and each earns its place for platform management. However, the server is titled 'CADE: Processos' yet only one tool is domain-specific, making the count feel imbalanced. A slightly smaller number of utility tools would better match the apparent purpose.

Completeness2/5

The server offers only a single domain operation ('cade_processos_consultar') for what appears to be a legal processes server. There are no list, get-details, or workflow operations beyond the one query, leaving significant gaps for common use cases. The rest of the tools are unrelated to the domain, focused on platform administration.

Resources