Alugar ou Comprar — MCP Server

calculate_cet

Calcula o CET (Custo Efetivo Total) anual de um financiamento imobiliário, incluindo juros, seguros MIP/DFI e taxas administrativas. Aceita os mesmos parâmetros da simulação comprar vs alugar.

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$)

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

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states what is calculated but does not mention return format, side effects, prerequisites, or whether it is read-only. For a calculation tool, this is acceptable in terms of side effects, but the absence of any output description leaves the agent guessing about the result structure.

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 sentences, front-loaded with the core purpose and a brief inclusion list. It wastes no words and is appropriately concise for a calculator tool.

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

Completeness2/5

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

Given the 30-parameter complexity and no output schema or annotations, this description is too thin. It does not explain what the tool returns, any dependencies between parameters, or how the CET calculation differs from other calculations. The completeness is low; the description only covers the basic purpose.

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?

Schema description coverage is 100%, so all 30 parameters are already documented. The description adds no specific parameter details beyond the general note about accepting same parameters as buy vs rent, which is not additional meaning for individual params. Baseline 3 applies because the schema handles parameter semantics adequately.

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 ('Calcula') and resource ('CET anual de um financiamento imobiliário'), listing included components (juros, seguros MIP/DFI, taxas administrativas). It is clear what the tool computes, though it does not explicitly contrast with sibling tools like simulate_buy_vs_rent, so it loses a point for not differentiating itself.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus the many siblings. The only hint is 'Aceita os mesmos parâmetros da simulação comprar vs alugar', which implies a relationship but does not state conditions for choosing this tool over alternatives. No exclusions or when-not-to-use advice.

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?