Skip to main content
Glama
Sign In

DecisionsCalc calculators

by com.decisionscalc
OverviewDiscussionsAdmin

ireland etf exit tax lots

ireland_etf_exit_tax_lots
Read-only

Ireland: exit tax on ETF purchases (lots): each lot’s 8-year deemed disposal dates, the tax due at each (41% to 2025, 38% in 2026, 35% from 2027 under Budget 2027) and the credit back when you sell. Values not given are grown at the rate you set (an assumption).

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": {
      "lots": "<lots>"
    },
    "name": "ireland_etf_exit_tax_lots"
  }
}

Input Schema

NameRequiredDescriptionDefault
lotsYesPurchases (up to 50)
untilNoShow events up to this date, YYYY-MM-DD (default 20 years from today)
growthNoGrowth % a year for values not given (default 5, an assumption)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, openWorldHint false), and the description still adds real substance: the rate schedule (41% to 2025, 38% in 2026, 35% from 2027) and the credit-back mechanism on sale. It also flags that unprovided values are grown by a user-set rate that is an assumption, which is important behavioural context for interpreting results.

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?

Two sentences, front-loaded with the resource and the outputs, with the rate schedule compressed into a parenthetical. The nested parentheses around the rate table are slightly dense but every clause carries domain information.

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 no output schema, the description does the work of telling the agent what comes back: deemed disposal dates, tax due per date, and credit on sale. Combined with a fully documented schema and read-only annotations, little an agent needs to call it correctly is missing, though the default 20-year horizon and 50-lot cap live only in the schema.

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 documents lots, bought, cost, sold, values, until and growth. The description only adds framing that the growth rate is an assumption, which is useful but marginal against a fully documented schema.

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 resource and output set: exit tax on ETF purchases by lot, each lot's 8-year deemed disposal dates, the tax due at each date, and the credit back on sale. This is clearly distinct from generic siblings such as ireland_capital_gains_tax, though no sibling is named explicitly.

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: an agent can infer this is for Irish ETF deemed-disposal exit tax calculations from the subject matter, but there is no explicit when-to-use statement, no exclusion of non-ETF gains, and no pointer to the capital gains tool as an alternative. It also omits the schema's 50-lot limit, which matters for when the tool is appropriate.

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