Skip to main content
Glama

Nível Socioeconômico e Renda Estimada

by io.github.mcp-dir

renda_estimada_consultar

Read-onlyIdempotent

Estimativa de nível socioeconômico e renda de uma pessoa física a partir do CPF, com base em renda, ocupação e escolaridade. 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.1/5.0
Behavior5/5

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

Annotations already indicate readOnly and idempotent, and the description adds valuable behavioral context: no credentials required, pay-per-query with prepaid credit, consults credit bureaus and official bases, and mandates LGPD compliance with the client as controller. These details go beyond annotations and give the agent a full picture of costs, data sources, and legal obligations.

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 paragraph of four sentences, each providing distinct information: purpose, hosting/pricing, data sources, and legal compliance. It is structured with the purpose first, and while somewhat dense, every sentence adds value. A 4 is appropriate for its efficient yet informative structure.

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?

With two parameters and no output schema, the description covers the core functionality and constraints well, but it omits details about the 'completo' parameter and expected response format. The legal and payment context is thorough, yet parameter clarification and output expectations are missing, making it average completeness for this complexity level.

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 compensate for parameter documentation. It mentions CPF implicitly ('a partir do CPF') but does not explain the 'completo' boolean parameter or any parameter semantics. This leaves agents guessing about the optional parameter's purpose, which is a significant gap given the lack of schema descriptions.

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: 'Estimativa de nível socioeconômico e renda de uma pessoa física a partir do CPF' (estimate socioeconomic level and income from CPF). It specifies the input (CPF) and the computation basis (income, occupation, education), distinguishing it from generic sibling tools like 'authenticate' or 'connect'.

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 on when to use the tool: it is a hosted, prepaid service that queries credit bureaus to estimate income, and requires a legal basis (e.g., risk analysis requested by the data subject). It does not explicitly mention alternatives or exclusions, but the sibling tools are unrelated, so the context is sufficient for selection.

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

All Nível Socioeconômico e Renda Estimada 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 are clearly distinct: renda_estimada_consultar, report_bug, show_version, and toolkit_info each have unique purposes. However, authenticate and connect overlap around authentication/connection status, and marketplace and toolkit_info share some visibility into installed tools, causing minor ambiguity.

Naming Consistency2/5

Tool names are inconsistent: some are English verbs (authenticate, connect, report_bug, show_version), some are English nouns (marketplace, toolkit_info), and the sole domain-specific tool is in Portuguese with an awkward noun_noun_verb structure (renda_estimada_consultar). No clear naming pattern emerges.

Tool Count3/5

The count of 7 tools is within a reasonable range, but the server's stated purpose is socioeconomic level and income estimation, while only one tool addresses that domain. The rest are generic platform utilities, making the set feel misaligned and somewhat bloated for the claimed focus.

Completeness2/5

For a server supposedly dedicated to income estimation, there is only a single 'consult' operation and no supporting tools (e.g., batch lookup, validation, or explanation of data sources). The large number of unrelated utility tools does not compensate for the lack of domain coverage, leaving significant gaps for agents seeking comprehensive socioeconomic data.

Resources