Skip to main content
Glama

30% ruling year by year (30%, 27% from 2027, the end after 5 years)

thirty_percent_ruling_timeline
Read-onlyIdempotent

Net income year by year for an employee with the Dutch 30% ruling: 30%, then 27% from 2027 for rulings that started in 2024 or later, the salary norm, the end of the ruling after five years, and Box 3 on Dutch and foreign assets (partial non-resident status only for rulings that started before 2024).

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": {
      "gross_annual": "<gross_annual>"
    },
    "name": "thirty_percent_ruling_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_yearNoYear the ruling started (January assumed), 2019-2026. Default 2025.
dutch_assetsNoSavings and investments in the Netherlands, euros. Default 0.
gross_annualYesGross annual salary in euros
fiscal_partnerNoHas a fiscal partner (double Box 3 allowance). Default false.
foreign_savingsNoSavings abroad, euros. Default 0.
foreign_investmentsNoInvestments abroad, euros. Default 0.
partial_non_residentNoChose partial non-resident status (only for rulings that started before 2024). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds substantive domain behavior beyond that: the 30%→27% rate change effective 2027 applies only to rulings starting 2024 or later, the ruling ends after five years, and partial non-resident status is valid only for pre-2024 rulings. It does not cover input validation or default behavior when start_year is omitted (schema handles that), so a 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with a colon-delimited enumeration of the model's components, front-loading the core output (net income year by year) before the qualifying rules. No filler or repetition of the title.

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?

For a 7-parameter deterministic calculator, the description conveys the model's scope (multi-year, ruling-expiry, Box 3 on Dutch and foreign assets) so an agent can judge fit without reading the schema. The one weak point is that with no output schema, the exact return shape (e.g. per-year rows and which fields) is only loosely implied by 'year by year'.

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 every parameter including defaults and ranges (2019-2026) is already documented in the schema. The description restates one parameter rule (partial non-resident only before 2024) but adds no syntax, units, or interaction details beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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 the exact resource and scope: net income year by year for a 30%-ruling employee, including the 2027 rate step-down, salary norm, five-year expiry, and Box 3 treatment. That distinguishes it implicitly from siblings like net_salary_netherlands (single-year net pay) and box3_wealth_tax, but it never says so explicitly, so it stops short of a 5.

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 presence of gross_annual and start_year signals a multi-year projection for ruling holders, and the parenthetical about partial non-resident status hints at a constraint. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. net_salary_netherlands for a single year), so it is minimum viable.

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.

Resources