Skip to main content
Glama

Certidão de Crimes Eleitorais (TSE)

by io.github.mcp-dir

tse_crimes_eleitorais_consultar

Read-onlyIdempotent

Emite a certidão de crimes eleitorais de uma pessoa no TSE a partir do nome, CPF, título e data de nascimento. 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
NomeYes
NomeMaeYes
completoNo
DataNascimentoYes
NumeroTituloEleitoralYes

Schema Changelog

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

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds meaningful context beyond annotations: hosting, no credentials needed, payment model, and the public/non-confidential nature of the data. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences with purpose front-loaded. The legal/disclaimer sentence adds necessary context without excessive verbosity. Every sentence earns its place.

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?

Covers purpose, auth, cost, and data sensitivity, but lacks parameter-level detail (especially required fields) and return format. Since there is no output schema, the description should explain the certificate more fully. Adequate but with clear gaps.

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 coverage is 0%, so the description must compensate. It mentions nome, CPF, título, and data de nascimento, but omits the required NomeMae and the optional 'completo' field. This is a significant gap that could cause an agent to miss required parameters.

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 a specific verb ('Emite a certidão') and resource ('crimes eleitorais de uma pessoa no TSE'), distinguishing it from the unrelated sibling tools. No ambiguity about what the tool does.

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: public access data, no credentials, pay-per-query, and LGPD responsibility. It doesn't explicitly compare to alternatives, but siblings are platform utilities unrelated to data queries, so no exclusion is needed.

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

All Certidão de Crimes Eleitorais (TSE) 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

Each tool has a distinct overall purpose, but the marketplace tool is a catch-all covering search, invoke, install, prompts, and more, while authenticate and connect overlap in handling credentials and connection status. This creates some ambiguity for an agent choosing between them, especially since the domain-specific tool is the only one actually related to the server's stated purpose.

Naming Consistency3/5

All names use lowercase snake_case, so there is no mixing of conventions, but the pattern is inconsistent: some are bare verbs (authenticate, connect), some are verb_noun (report_bug, show_version), one is a noun (marketplace), and the domain tool is a long descriptive phrase. This makes the set readable but not predictable.

Tool Count2/5

At 7 tools, the count is within a typical range, but 6 of them are generic platform utilities that do not relate to the server's stated TSE certidão domain. This bloats the tool list for a service whose actual scope is a single lookup operation, making the count feel inappropriate for the apparent purpose.

Completeness3/5

The one domain tool covers the core action of emitting a certidão, but there are no supporting operations such as verifying a certidão, checking request history, or listing available certidões. The platform tools do not contribute to the domain, so the surface is narrowly functional but lacks any lifecycle or auxiliary operations.

Resources