Skip to main content
Glama

What the 2027 Dutch tax plan means for a salary

dutch_tax_changes_2027
Read-onlyIdempotent

Compares income tax on a gross salary in 2026 with the Belastingplan 2027 proposal (presented on Prinsjesdag 2026, a proposal until Parliament votes): brackets and tax credits, and the 30% ruling dropping to 27% unless it 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": "dutch_tax_changes_2027"
  }
}

Input Schema

NameRequiredDescriptionDefault
gross_annualYesGross annual salary in euros, without holiday allowance
thirty_percent_rulingNoHas the 30% ruling. Default false.
ruling_started_before_2024NoThe ruling started before 2024 (keeps 30% in 2027). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real domain context: the 2027 figures are a proposal until Parliament votes, and the 30% ruling falls to 27% unless it predates 2024. It does not describe the shape of the comparison output, which keeps it short of a 5.

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 dense sentence with the comparison scope front-loaded, followed by the two relevant mechanics. It is packed with parentheticals but every clause earns its place; only a slightly heavy single-sentence structure holds it back from a 5.

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 three-parameter read-only calculator with no output schema, the description conveys the comparison basis, the tax elements included, and the proposal's legal status. It does not state what the returned comparison looks like, which is the only material gap.

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, but the description adds mechanism the schema only asserts: why ruling_started_before_2024 matters (30% is retained for pre-2024 rulings) and that brackets and credits are part of the computation. That is genuine meaning beyond the field labels.

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 verb (compares) and resource (income tax on a gross salary) and scopes it precisely to 2026 vs the Belastingplan 2027 proposal. That framing distinguishes it from siblings like net_salary_netherlands and visa_salary_check, which do not compare the reform scenario.

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?

The scenario is clearly implied (agent should use this when the question is about the 2027 plan rather than current-year net pay), but no sibling is named and no explicit when-not condition is given. An agent must infer the routing from the sibling list.

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