Skip to main content
Glama

ireland rent tax credit

ireland_rent_tax_credit
Read-onlyIdempotent

Ireland: how much Rent Tax Credit a renter can claim for each year 2022–2026 (20% of rent, capped per year), including back-claims. Claims for 2022 must be made by 31 December 2026 (Revenue four-year rule).

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": {
      "monthlyRent": "<monthlyRent>"
    },
    "name": "ireland_rent_tax_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
coupleNoJointly assessed married couple or civil partners
monthlyRentYesRent paid a month, EUR (same every year)

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. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already make clear this is a safe, read-only, idempotent calculation, so the description does not need to explain side effects. It adds useful behavioral context by disclosing the 20% calculation basis, per-year cap, back-claim handling, and the four-year claim deadline.

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?

The definition is a single front-loaded sentence with no unrelated filler, and the key scope and formula are stated first. It is dense with useful caveats, but the nested parentheticals make it slightly less immediately scannable than it could be.

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?

Given the annotations, full input-schema descriptions, and presence of an output schema, the description supplies the key tax computation context an agent needs. It does not detail eligibility beyond the renter framing, but that is a minor gap for this focused calculator.

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 coverage is 100%, so both parameters are already documented in the input schema. The description explains the calculation rules at a high level but does not add parameter-specific meaning, for example how the couple flag changes the calculation beyond the schema note that it means jointly assessed married couples or civil partners.

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 names a specific credit and states exactly what it computes: the Rent Tax Credit a renter can claim for each year 2022–2026, including the 20% rate, annual cap, and back-claims. The renter focus also distinguishes it from landlord-oriented siblings such as ireland_landlord_rental_tax.

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?

It clearly establishes the applicable context: a renter calculating the credit for 2022–2026, including back-claims. It also gives the important 31 December 2026 deadline for 2022 claims under the Revenue four-year rule, though it does not explicitly name alternatives or state when not to use the tool.

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.