Skip to main content
Glama

PEP Estendida (Parentescos)

by io.github.mcp-dir

pep_parentescos_consultar

Read-onlyIdempotent

Verifica se uma pessoa é Politicamente Exposta (PEP) ou tem parentesco com um PEP, a partir do CPF. 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
completoNo

Schema Changelog

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

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds valuable context: payment via prepaid credit, no credentials required, data is public access, and LGPD responsibility. This goes beyond annotations and helps the agent understand cost and legal implications.

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 concise and front-loaded with the primary purpose, followed by relevant operational details (cost, credentials, data source). The LGPD sentence adds legal context but is not excessive. It is appropriately sized for the tool's simplicity.

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?

Given no output schema, the description should describe return values or behavior, but it does not. It covers purpose, access, cost, and legal role, but omits the meaning of the 'completo' parameter and any output format. This makes it only partially complete for an agent to invoke correctly.

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 must explain parameters. It clarifies 'Cpf' by stating 'a partir do CPF', but 'completo' (a boolean) is left completely undefined. This is a significant gap that the description does not compensate for.

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: 'Verifica se uma pessoa é PEP ou tem parentesco com um PEP, a partir do CPF.' This provides a specific verb (verifica), resource (person via CPF), and differentiates from sibling tools which are generic (authenticate, connect, etc.).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (checking PEP status) but does not explicitly state when to use this tool vs alternatives, nor does it mention any exclusions. It mentions 'sem credenciais' and 'pague por consulta' but these are access details, not usage guidelines.

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

All PEP Estendida (Parentescos) 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.9/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: auth handles login, connect reports connection status, marketplace manages the MCP catalog, pep_parentescos_consultar performs the domain query, and the rest are utility/feedback/version tools. However, connect and toolkit_info both provide connection/status information, which could cause an agent to select the wrong one.

Naming Consistency3/5

Naming style is mixed: some tools are single verbs (authenticate, connect), some are verb_noun (report_bug, show_version), some are nouns (marketplace, toolkit_info), and the domain tool uses a different convention (pep_parentescos_consultar). Although all are lowercase with underscores, the lack of a consistent verb/noun pattern reduces predictability.

Tool Count3/5

Seven tools is within the typical range, but the server's declared domain (PEP parentescos) is covered by only one tool; the rest are platform-level utilities (auth, marketplace, version, etc.). This makes the tool count feel inflated relative to the domain purpose, though it is not extreme.

Completeness4/5

The domain tool provides the core capability (PEP/relationship check via CPF) and is backed by platform tools for authentication, payment, and status. There are no obvious dead ends, though there is no consult history or batch operation, which would be minor enhancements.

Resources