Alugar ou Comprar — MCP Server

recommendation_contextual

Gera uma recomendação contextual entre alugar e comprar, considerando horizonte de permanência e sensibilidade aos parâmetros de valorização do imóvel e rendimento do investimento alternativo. Retorna horizonte de corte (breakeven patrimonial), veredito ano a ano, thresholds de sensibilidade e um texto de recomendação pronto para o usuário.

Input Schema

TableJSON Schema

Name	Required	Description
`cetPct`	No	CET (Custo Efetivo Total) anual informado (%)
`itbiPct`	No	ITBI (% do valor do imóvel)
`prazoAnos`	No	Prazo do financiamento em anos
`seguroPct`	No	Seguro anual do financiamento (% do valor do imóvel)
`trHistory`	No	Série mensal de TR (% a.m.), ex: [0.0052, 0.0048, ...]
`entradaPct`	No	Percentual de entrada (%)
`inflacaoPct`	No	Inflação anual esperada (%)
`trMensalPct`	No	Taxa mensal de referência TR (%) para correção do saldo devedor
`valorImovel`	Yes	Valor do imóvel (R$)
`iptuAnualPct`	No	IPTU anual (% do valor do imóvel)
`aluguelMensal`	Yes	Aluguel mensal inicial (R$)
`fgtsDisponivel`	No	Saldo do FGTS disponível para entrada ou amortização (R$)
`rentIncreasePct`	No	Reajuste anual do aluguel (%)
`spreadOverTRPct`	No	Spread anual sobre a TR quando indexer = TR_PLUS_SPREAD (%)
`financingIndexer`	No	Indexador do financiamento: FIXA, TR ou TR_PLUS_SPREAD
`insuranceMonthly`	No	Seguro MIP/DFI mensal fixo em R$
`amortizationSystem`	No	Sistema de amortização (PRICE ou SAC)
`taxaValorizacaoPct`	No	Taxa anual de valorização do imóvel (%)
`custosManutencaoPct`	No	Custos anuais de manutenção (% do valor do imóvel)
`custoOportunidadePct`	No	Rendimento anual alternativo do capital (%)
`tempoPermanenciaAnos`	No	Horizonte de permanência em anos
`amortizacaoExtraMensal`	No	Amortização extra mensal (R$)
`taxasTransacaoVendaPct`	No	Total de taxas de transação de venda (% do valor do imóvel)
`taxasTransacaoCompraPct`	No	Total de taxas de transação de compra (% do valor do imóvel)
`administrativeFeeMonthly`	No	Taxa administrativa fixa mensal em R$
`taxaAdministrativaMensal`	No	Taxa administrativa mensal do banco (R$)
`rendaExtraMensalInvestida`	No	Renda extra mensal investida pelo comprador (R$)
`condominioMensalPctOfValue`	No	Condomínio mensal (% do valor do imóvel)
`taxaFinanciamentoNominalPct`	No	Taxa de juros nominal anual do financiamento (%)
`amortizacaoExtraordinariaMensal`	No	Amortização extraordinária mensal (R$)

Output Schema

TableJSON Schema

Name	Required	Description
`textoRecomendacao`	Yes	Texto formatado com horizontes de corte e thresholds de sensibilidade
`horizonteCorteAnos`	Yes	Número de anos até o breakeven patrimonial (ou null se não houver)
`thresholdsSensibilidade`	Yes
`recomendacaoPorHorizonte`	Yes	Veredito ano a ano para cada horizonte de permanência

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 4, 2026

addedInput schema / properties / amortizacaoExtraordinariaMensal

Added value: +{
+  "description": "Amortização extraordinária mensal (R$)",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / rendaExtraMensalInvestida

Added value: +{
+  "description": "Renda extra mensal investida pelo comprador (R$)",
+  "minimum": 0,
+  "type": "number"
+}

AddedSep 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It usefully states that the tool returns a breakeven horizon, year-by-year verdict, sensitivity thresholds, and a recommendation text. It does not explicitly state whether the operation has side effects or is read-only, though the wording strongly suggests a pure computation.

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?

The description is two concise, front-loaded sentences that state the purpose and the exact outputs with no filler. It covers substantial content despite the tool's high parameter count, and every clause earns its place.

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

Completeness4/5

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

Given a rich 100%-described schema, an output schema, and no annotations, the description supplies the missing conceptual framing: a contextual recommendation tool with breakeven and sensitivity outputs. It could add sibling differentiation, but that gap is covered under usage guidelines. Overall, an agent has enough to understand the tool's role and expectations.

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

Parameters3/5

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

The input schema has 100% parameter description coverage, so the description does not need to document individual parameters. It adds conceptual value by identifying horizon, property appreciation, and alternative investment return as sensitivity drivers. It provides no additional syntax, defaults, or parameter relationship details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Gera), resource (recomendação contextual entre alugar e comprar), and enumerates concrete outputs like breakeven horizon, year-by-year verdict, and sensitivity thresholds. However, it does not explicitly differentiate itself from close siblings like simulate_buy_vs_rent or sensitivity_analysis.

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 use when a contextual buy-vs-rent recommendation is needed, especially when horizon and sensitivity to appreciation and opportunity cost matter. It gives no explicit when-to-use or when-not-to-use guidance and never references sibling tools, so the selection is left to inference.

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

All Alugar ou Comprar — MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?