DecisionsCalc calculators

ireland pension tax relief

ireland_pension_tax_relief

Read-onlyIdempotent

Ireland: income tax relief on personal pension contributions and AVCs (occupational scheme, PRSA, RAC, PEPP): the age-related limit (under 30 15%, 30-39 20%, 40-49 25%, 50-54 30%, 55-59 35%, 60+ 40% of earnings up to €115,000), relief at the marginal rate (2026 or Budget 2027 bands; no USC or PRSI relief), the net cost and the room left this year.

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>",
      "pay": "<pay>",
      "contributions": "<contributions>"
    },
    "name": "ireland_pension_tax_relief"
  }
}

Input Schema

Name	Required	Description
`age`	Yes	Age in the tax year
`pay`	Yes	Gross earnings from the job, EUR
`year`	No	Tax year
`status`	No	Tax status
`spousePay`	No	Spouse gross salary (married-two), EUR
`contributions`	Yes	Own contributions this year incl. AVCs, EUR

Output Schema

Name	Required	Description
`next`	No	Optional paid follow-on (name, url, what) where it genuinely helps
`note`	No	When the figures were read, and that this is general information, not advice
`page`	Yes	The calculator page to cite or link, https://decisionscalc.com/...
`result`	Yes	The calculation (usually an object), same engine and figures as the calculator page
`sources`	Yes	Official source URLs for the figures used

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026

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

AddedNov 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds domain behavior beyond that: relief is at the marginal rate only (no USC or PRSI relief), earnings are capped at €115,000, and the result includes net cost and remaining room. It does not note assumptions such as earnings being from the job or how partial contributions interact with the cap.

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?

It is one long but front-loaded sentence that leads with the jurisdiction and the exact relief computed, then packs the age table and rate rules into parentheses. Every clause carries domain information, though the heavy parenthetical nesting makes it dense to parse at a glance.

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?

With an output schema present, the description need not explain return values, and it supplies the core tax rules (age bands, €115,000 cap, marginal-rate-only relief) plus what the output covers via 'net cost and the room left this year'. What is missing is minor: eligibility prerequisites and any treatment of the year/status inputs beyond the schema's own 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; the description earns above that by explaining how inputs drive the result — age selects the percentage band (15%–40%), pay is subject to the €115,000 cap, and contributions include AVCs. It still leaves year/status/spousePay semantics entirely to the schema (e.g. how married-two splits the bands).

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+resource: income tax relief on personal pension contributions and AVCs, and enumerates the covered scheme types (occupational, PRSA, RAC, PEPP). It also scopes what is computed (age-related percentage limit, marginal-rate relief, net cost, remaining room), which implicitly separates it from sibling pension tools like state pension or MyFutureFund. It stops short of explicitly naming any sibling, so it is clear but not fully differentiated.

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?

Usage is only implied: the description reads as a relief calculator for a given age/pay/contribution scenario, and the mention of 2026 or Budget 2027 bands hints at when each applies. There is no explicit when-to-use/when-not statement, no prerequisites (e.g. that relief requires relevant earnings), and no pointer to an alternative tool.

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

All DecisionsCalc calculators 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.