Skip to main content
Glama

ireland overpay mortgage or invest

ireland_overpay_mortgage_or_invest
Read-onlyIdempotent

Ireland: overpay the mortgage, invest, or top up a pension? Compares the same lump sum and/or extra monthly amount four ways at a horizon, after Irish tax: overpaying (keep the payment and shorten the term, or reduce the payment; interest saved, months cut, a tax-free return equal to the mortgage rate, freed payments saved after 33% DIRT), an Irish/EU ETF or fund (exit tax 38% in 2026, 35% from 2027, 8-year deemed disposal with credit), shares or an investment trust (CGT 31% above the €1,270 exemption) and a pension AVC/PRSA (relief at 20% or 40% within the age-related limit of 15%-40% of earnings up to €115,000; 25% lump sum tax-free up to €200,000, the rest taxed at the retirement rate; flags when it is still locked at the horizon). Returns the ranking, a plain verdict and the break-even growth rate at which each investment matches overpaying. Use this when someone in Ireland asks whether to overpay their mortgage or invest (ETFs, shares) or make pension AVCs, or whether to reduce the term or the payment; for a lump sum with no mortgage, use ireland_where_to_put_savings.

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": {
      "balance": "<balance>",
      "ratePct": "<ratePct>",
      "termYears": "<termYears>",
      "marginalRate": "<marginalRate>",
      "age": "<age>"
    },
    "name": "ireland_overpay_mortgage_or_invest"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesAge now
payNoGross pay a year for the pension limit, EUR (default 60000)
modeNoAfter overpaying: keep the payment and shorten the term (default), or reduce the payment
balanceYesMortgage balance, EUR
lumpSumNoLump sum available now, EUR (default 0)
ratePctYesMortgage interest rate, % a year
accessAgeNoAge the pension can be drawn (default 60)
growthPctNoMarket growth % a year after charges (default 5, an assumption)
termYearsYesYears left on the mortgage
horizonYearsNoCompare after this many years (default 10)
marginalRateYesIncome tax rate now, 20 or 40
monthlyExtraNoExtra amount each month, EUR (default 0)
depositRatePctNoDeposit rate for freed payments, % AER (default 2.5)
retirementRateNoIncome tax rate in retirement, 20 or 40 (default: same as now)
pensionContributionsNoOwn pension contributions already paid each year, EUR (default 0)

Output Schema

NameRequiredDescriptionDefault
nextNoOptional paid follow-on (name, url, what) where it genuinely helps
noteNoWhen the figures were read, and that this is general information, not advice
pageYesThe calculator page to cite or link, https://decisionscalc.com/...
resultYesThe calculation (usually an object), same engine and figures as the calculator page
sourcesYesOfficial source URLs for the figures used

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "next": {
      +      "description": "Optional paid follow-on (name, url, what) where it genuinely helps",
      +      "properties": {
      +        "name": {
      +          "type": "string"
      +        },
      +        "url": {
      +          "type": "string"
      +        },
      +        "what": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "note": {
      +      "description": "When the figures were read, and that this is general information, not advice",
      +      "type": "string"
      +    },
      +    "page": {
      +      "description": "The calculator page to cite or link, https://decisionscalc.com/...",
      +      "type": "string"
      +    },
      +    "result": {
      +      "description": "The calculation (usually an object), same engine and figures as the calculator page"
      +    },
      +    "sources": {
      +      "description": "Official source URLs for the figures used",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "result",
      +    "page",
      +    "sources"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description goes well beyond them: it discloses the tax model applied (38%/35% exit tax with 8-year deemed disposal, 31% CGT above the €1,270 exemption, DIRT on freed payments, pension relief bands and 25% lump sum cap) and flags the edge case that pension money may still be locked at the horizon. This is exactly the modelling context an agent needs to trust and frame the result.

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?

Front-loaded with the decision question and closed with the usage/alternative guidance, and every clause carries a tax fact that affects the comparison. The middle is a single very dense semicolon-and-parenthesis run that is hard to parse on first read, which keeps it from a 5.

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

Completeness5/5

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

For a 15-parameter, high-complexity modelling tool with an output schema and annotations already supplied, the description covers purpose, tax assumptions, output shape (ranking, verdict, break-even growth rate) and sibling routing. Nothing material an agent needs before calling it is missing.

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 coverage is 100%, so baseline is 3; the description adds real meaning by explaining the two post-overpayment modes (keep payment and shorten term vs reduce payment), what "same lump sum and/or extra monthly amount" means as inputs, and the role of marginal vs retirement rate. It does not individually explain pensionContributions, depositRatePct, or accessAge beyond the schema text.

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?

States a specific decision question (overpay mortgage vs invest vs pension AVC) with the exact comparison dimensions (same lump sum and/or extra monthly amount, at a horizon, after Irish tax) and names the sibling it is not (ireland_where_to_put_savings). An agent can distinguish this from ireland_investment_account_vs_etf_vs_pension or ireland_pension_tax_relief without opening any schema.

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

Usage Guidelines5/5

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

Explicit when-to-use clause ("Use this when someone in Ireland asks whether to overpay their mortgage or invest (ETFs, shares) or make pension AVCs, or whether to reduce the term or the payment") plus an explicit exclusion routing lump-sum-with-no-mortgage cases to ireland_where_to_put_savings. Both the trigger and the boundary are stated, not inferred.

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.