Skip to main content
Glama
Sign In

DecisionsCalc calculators

by com.decisionscalc
OverviewDiscussionsAdmin

ireland fair deal contribution

ireland_fair_deal_contribution
Read-only

Ireland Nursing Homes Support Scheme (Fair Deal): the weekly contribution (80% of assessable income and 7.5% a year of assets over €36,000; a couple 40% of combined income and 3.75% over €72,000), what the HSE pays, the contribution after the 3-year cap on the home, and the Nursing Home Loan balance after 5 years.

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": {
      "costWeekly": "<costWeekly>",
      "incomeWeekly": "<incomeWeekly>"
    },
    "name": "ireland_fair_deal_contribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
coupleNoA spouse or partner still lives at home
savingsNoSavings and other assets, EUR
useLoanNoUse the Nursing Home Loan (default true)
costWeeklyYesNursing home’s agreed weekly price, EUR
homeEquityNoHome value less mortgage, EUR
spncWeeklyNoMaximum State Pension (Non-Contributory) a week, if known (raises the allowance kept)
incomeWeeklyYesAssessable income a week, EUR (a couple: combined)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral content beyond that – the 80%/7.5% assessment rules, the couple variants, the 3-year cap, and the 5-year loan balance – but says nothing about assumptions, rounding, defaults (e.g. useLoan default true), or edge cases like zero home equity.

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?

One front-loaded sentence that names the scheme before the parenthetical formulas, with no filler. The dense nested parentheticals make it slower to scan than a short bulleted structure would be, but nothing is redundant.

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?

The description names the four outputs it produces, which stands in for the missing output schema, and covers the core assessment rules for a 7-parameter calculator. Gaps remain on default handling for useLoan and on what spncWeekly changes concretely, but the essential picture is present.

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 the schema already carries parameter meaning; the baseline is 3. The description reinforces the couple scaling (40% of combined income, 3.75% over €72,000) and the asset threshold, but adds no clarification on useLoan, spncWeekly, or how savings and homeEquity combine.

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?

States a specific scheme (Ireland Nursing Homes Support Scheme / Fair Deal) and enumerates the outputs it computes: weekly contribution, what the HSE pays, contribution after the 3-year cap, and Nursing Home Loan balance. It is clear what the tool does, though it never contrasts itself with the closest sibling (uk_care_home_fees) or distinguishes from generic retirement calculators.

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 by the scheme name and the euro-denominated inputs; there is no explicit statement of when to use this versus uk_care_home_fees or ireland_can_i_retire, and no mention of eligibility prerequisites or when-not-to-use. An agent can infer the domain but gets no routing guidance.

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

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

Resources