Skip to main content
Glama

ireland can i retire

ireland_can_i_retire
Read-only

Ireland: can I retire at 60 (or any age)? Year-by-year projection to 95 for one person or a couple: pay and pension contributions until retirement, DC pots drawn at retirement (25% lump sum: first €200,000 tax-free, next €300,000 at 20%; the rest to an ARF with the 4%/5%/6% imputed minimum drawdown), DB pensions, State Pension (Contributory) from 66 (default €309.30 a week, 2027), savings, an optional UK State Pension for UK years (from the UK State Pension age, taxed in Ireland, no USC), a spending target in today’s money, and income tax (age credit, €18,000/€36,000 exemption with marginal relief), USC (none on the State Pension; reduced at 70+) and PRSI (pay only) on the 2027 rules. Growth and inflation are assumptions. Returns the age the money lasts to, bridge years before 66, wealth at retirement, the spending that lasts to 95, retire-at-60/62/65 comparison and key years in today’s money.

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": {
      "age": "<age>",
      "retireAge": "<retireAge>",
      "spending": "<spending>"
    },
    "name": "ireland_can_i_retire"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesYour age now
growthNoPension/ARF growth % a year after charges (default 4.5, an assumption)
salaryNoGross pay a year, EUR
savingsNoSavings and investments outside pensions, EUR
spendingYesHousehold spending a year in retirement after tax, today’s money, EUR
dbFromAgeNoAge the DB pension starts
dbPensionNoDefined benefit pension a year, EUR (0 if none)
householdNoHousehold
inflationNoInflation % a year (default 2)
retireAgeYesAge you stop work
contribPctNoYour pension contributions, % of pay
partnerAgeNoPartner age now
pensionPotNoDC pension pots today (occupational DC, PRSA, AVC), EUR
savingsAddNoAdded to savings each year until retirement, EUR
employerPctNoEmployer contributions, % of pay
partnerSalaryNoPartner gross pay a year, EUR
ukPensionWeeklyNoUK State Pension forecast a week in pounds (overrides ukQualifyingYears)
partnerDbPensionNoPartner DB pension a year, EUR
partnerRetireAgeNoPartner retirement age
partnerPensionPotNoPartner DC pension pots, EUR
ukQualifyingYearsNoUK National Insurance qualifying years (UK State Pension: 1/35 of £241.30 a week each, 10 minimum)
statePensionWeeklyNoExpected State Pension a week in 2027 euros (full rate 309.30; 0 if none)
partnerStatePensionWeeklyNoPartner State Pension a week (2027 euros)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description adds substantial behavioral context: the 2027 tax basis, drawdown rules (25% lump sum, ARF imputed minimums), UK pension taxation treatment, default State Pension rate, and the exact outputs returned. This is far beyond what the annotations alone provide.

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 core purpose is front-loaded, but the description is a dense, run-on paragraph with parenthetical tax rules that is difficult to parse. For a complex 23-parameter calculator, length is justified, but the structure could be improved with clearer sentence breaks or grouping.

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?

Despite having no output schema and 23 parameters, the description explains the assumptions, the tax rules applied, the key outputs (age money lasts, bridge years, wealth at retirement, 60/62/65 comparison), and the treatment of optional inputs. An agent has enough context to invoke it correctly without further documentation.

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 the baseline is 3, but the description adds meaningful semantics for several parameters—e.g., the tax treatment of the UK State Pension, the default €309.30 weekly State Pension for 2027, and how the DC pot is drawn down. This contextual framing helps the agent understand what inputs like pensionPot and ukPensionWeekly represent.

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 calculation: a year-by-year retirement projection to age 95 for a single person or couple, modelling DC/DB pensions, State Pension, savings, UK pension, and Irish taxes. It clearly distinguishes this broad planning tool from narrower siblings like ireland_state_pension_contributory or ireland_pension_tax_relief.

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 phrase 'can I retire at 60 (or any age)?' implies the use case, but there is no explicit instruction on when to choose this tool over sibling calculators, nor any stated exclusions or prerequisites. Usage is inferable but not guided.

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.