Skip to main content
Glama

Análise de Crédito PF Completa

by io.github.mcp-dir

credito_pf_completo_consultar

Read-onlyIdempotent

Análise completa de crédito de uma pessoa física a partir do CPF: dados cadastrais, score, pendências e histórico. 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
CPFYes
completoNo

Schema Changelog

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

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds valuable context beyond annotations: no credentials, prepaid payment, queried bureaus, and LGPD/legal basis obligations. This enriches the agent's understanding of operational and compliance aspects.

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 sentences, each adding meaningful information: purpose, operational context, and legal note. No redundancy or 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?

The description covers purpose, data sources, pricing, and legal basis, but the unexplained 'completo' parameter is a clear gap. Without an output schema or parameter descriptions, the tool is not fully specified.

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?

With 0% schema description coverage, the description must compensate. It provides context for the CPF parameter ('a partir do CPF') but completely omits the boolean 'completo' parameter, leaving its function ambiguous. This is a significant gap for a tool with only two 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 the tool performs a complete credit analysis of an individual from CPF, enumerating the data types (registration data, score, pendencies, history). This specific verb+resource combination distinguishes it from the unrelated 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: hosted by the platform, no credentials, prepaid credit per consultation, and legal basis requirement. It doesn't explicitly exclude alternatives, but no similar sibling exists, so the context is sufficient for usage.

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

All Análise de Crédito PF Completa 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

The credit analysis tool is clearly distinct, but several platform tools overlap: authenticate, connect, and toolkit_info all deal with connection/auth status, and marketplace is a mega-tool covering many actions. This overlap could cause an agent to select the wrong utility.

Naming Consistency2/5

Names mix English verbs (authenticate, connect), English verb_noun (report_bug, show_version), nouns (marketplace, toolkit_info), and a Portuguese compound (credito_pf_completo_consultar). There is no consistent naming pattern across the set.

Tool Count3/5

Seven tools is within a typical range, but only one tool serves the credit analysis domain; the other six are generic platform utilities. The set feels padded relative to the server's stated purpose.

Completeness4/5

The single credit tool covers the full consultation: cadastral data, score, pending issues, and history. Minor gaps exist (e.g., no direct balance or query history), but the marketplace can handle payment top-ups indirectly.

Resources