Skip to main content
Glama

ireland sell or keep rental

ireland_sell_or_keep_rental
Read-only

Ireland: should a landlord sell a rental property now or keep it? Compares wealth after tax year by year over N years (default 10): KEEP = rent (growth capped at 2% or CPI under the rent control from 1 March 2026) less costs, mortgage and Case V tax at the marginal rate, plus growth, valued net of selling costs, CGT and any RPRIR clawback; SELL NOW = price less selling costs, CGT (31% from 7 October 2026, €1,270 exemption, pre-2003 indexation) and the mortgage, invested in State Savings, a deposit (DIRT), an ETF (exit tax, deemed disposal), a pension (age limits) or the home mortgage. Returns the difference, both paths by year, the break-even house-price growth and year-1 income.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "value": "<value>",
      "purchasePrice": "<purchasePrice>",
      "rent": "<rent>"
    },
    "name": "ireland_sell_or_keep_rental"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoYour age
payNoYour gross salary a year, EUR
rentYesRent a year, EUR
costsNoDeductible costs a year, EUR
valueYesWhat the property would sell for now, EUR
yearsNoYears to compare (1-30)
statusNoTax status
rentGrowthNoRent growth, % a year
depositRateNoDeposit rate, %
houseGrowthNoHouse-price growth, % a year
investReturnNoETF and pension return, % a year
mortgageRateNoMortgage rate, %
purchaseDateNoDate bought, YYYY-MM-DD
mortgageYearsNoYears left on the mortgage
purchasePriceYesPrice paid, EUR
mortgageBalanceNoMortgage owed, EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real burden and does well: it discloses the modelling methodology, rent-control capping from 1 March 2026, CGT at 31% from 7 October 2026 with the €1,270 exemption and pre-2003 indexation, and the four reinvestment vehicles. Gaps are caveats rather than mechanics — it does not say the figures are estimates rather than advice, nor how defaults are assigned to omitted parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening question is well front-loaded, but the second sentence is a single dense block cramming in tax rates, dates, and five investment options. Every clause carries substance, yet the lack of internal structure makes it harder to scan than it needs to be for an agent parsing it in one pass.

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 16-parameter financial model with no output schema, the description does the necessary work by naming the return payload: the difference, both paths year by year, the break-even house-price growth, and year-1 income. What is thin is how status, pay, and age drive the marginal tax rate, leaving an agent to infer that link.

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 every one of the 16 parameters is already documented, and the baseline is 3. The description adds limited new meaning: the only genuinely new detail is the default of 10 years, which the schema omits while stating the 1-30 range. Concepts like marginal-rate Case V tax and the €1,270 CGT exemption add interpretive context but do not map back to individual fields such as status, pay, or age.

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 states a specific decision problem with a named resource: whether an Irish landlord should sell a rental property now or keep it. It is clearly distinct from siblings such as ireland_landlord_rental_tax (ongoing tax computation) or ireland_where_to_put_savings (general investment comparison), so an agent can select it without opening the schema.

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 phrase 'should a landlord sell a rental property now or keep it?' gives a clear context for use, and the two modelled paths (KEEP vs SELL NOW) make the scope explicit. However, it never names the neighbouring tools it should be preferred over, or states exclusions such as 'not for ongoing rental tax reporting' or 'not for non-landlords'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.