Alugar ou Comprar — MCP Server

sensitivity_analysis

Executa uma análise de sensibilidade cruzando taxas de valorização do imóvel com rendimentos do investimento alternativo. Retorna uma matriz onde cada célula indica se compensa comprar (C) ou alugar (A), além do ano de breakeven patrimonial. Reusa o mesmo motor de simulação de simulate_buy_vs_rent.

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$
`appreciationRates`	No	Valores de valorização anual do imóvel (%) para as linhas da matriz
`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
`investmentReturnRates`	No	Valores de rendimento anual do investimento alternativo (%) para as colunas da matriz
`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$)

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"
+}

Changed4 schema fields changedSep 2, 2026

addedInput schema / properties / amortizacaoExtraMensal

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

addedInput schema / properties / fgtsDisponivel

Added value: +{
+  "description": "Saldo do FGTS disponível para entrada ou amortização (R$)",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / taxaAdministrativaMensal

Added value: +{
+  "description": "Taxa administrativa mensal do banco (R$)",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / trMensalPct

Added value: +{
+  "description": "Taxa mensal de referência TR (%) para correção do saldo devedor",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "number"
+}

First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the output as a matrix with C/Alugar labels and breakeven year, and it reveals that the calculation reuses simulate_buy_vs_rent's simulation engine. It does not mention side effects, but the compute-and-return nature is reasonably clear.

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?

Two dense sentences: the first states the core operation and output, the second adds the engine reuse. No filler or repeated schema information.

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?

For a 32-parameter tool without an output schema, the description is on the shorter side, but it covers the essential decision output and the relationship to simulate_buy_vs_rent. The 100% schema coverage compensates for the parameters; the main missing information is explicit guidance on the required appreciation/investment arrays and matrix orientation.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds semantic value by linking the two matrix axes to appreciation rates and alternative returns and by explaining what each cell means, which is not fully captured by the individual parameter 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 opens with a specific verb and resource ('Executa uma análise de sensibilidade'), names the two crossed dimensions, and states the matrix output with C/A decisions and breakeven year. It is easy to distinguish from simulate_buy_vs_rent because it frames the multi-scenario sweep rather than a single scenario.

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 crossing of property appreciation rates with alternative investment returns clearly implies the tool is for sweeping over those two dimensions. The final sentence ties it to simulate_buy_vs_rent's engine, giving the agent context, though it does not explicitly say 'use this instead of simulate_buy_vs_rent' or list exclusions.

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?