Skip to main content
Glama

Tax in the year you move to or leave the Netherlands (M-form)

arrival_departure_year_m_form
Read-onlyIdempotent

For the year someone arrives in or leaves the Netherlands (the M-form, migration tax return): the salary earned while resident, the Dutch tax on it with the tax credits for that part of the year, and the net pay a month during the resident period.

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": {
      "scenario": "<scenario>",
      "date": "<date>",
      "gross_annual": "<gross_annual>"
    },
    "name": "arrival_departure_year_m_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesRegistration date in the municipality (arriving) or departure date (leaving), YYYY-MM-DD, 2024-2026
scenarioYesMoving to the Netherlands or leaving it
gross_annualYesGross salary for a full year at this pay, euros
thirty_percent_rulingNoThe 30% ruling applies. Default false.
holiday_allowance_on_topNoAdd 8% holiday allowance. 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 establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral context beyond that: it explains that the calculation covers only the resident period and includes partial-year tax credits and monthly net pay during that period.

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?

The description is a single, front-loaded sentence that immediately names the scenario and then lists the relevant outputs. Every clause earns its place by specifying either the tax context or a return component.

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 must carry the return-value burden, and it does so by enumerating resident-period salary, Dutch tax, tax credits, and monthly net pay. It does not discuss estimation assumptions or limitations, but the core calculation context is adequately covered.

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 all five parameters, including date, scenario, gross_annual, and the optional rulings. The description hints at partial-year proration via 'while resident' and 'for that part of the year,' but it does not add parameter-level syntax or mapping beyond the 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 clearly states the specific scenario (arrival/departure year, M-form migration tax return) and enumerates the outputs: resident-period salary, Dutch tax with partial-year credits, and monthly net pay. It is more specific than a generic tax calculator, but it does not explicitly contrast itself with sibling tools such as net_salary_netherlands or income_tax_return_netherlands.

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 implied by the phrase 'For the year someone arrives in or leaves the Netherlands,' which scopes the tool to migration years. However, the description gives no explicit when-to-use/when-not-to-use guidance or named alternatives for full-year residents or other tax scenarios.

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