Skip to main content
Glama

What you keep of a raise: tax plus lost allowances (poverty trap)

marginal_rate_allowance_cliff
Read-onlyIdempotent

For a salary in the Netherlands in 2026: the allowances a household gets (healthcare and rent allowance, child budget), the net income including them, and the share of the next €1,000 of salary that is kept after extra income tax and lost allowances. Also lists the salary ranges where a raise is mostly lost.

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": "marginal_rate_allowance_cliff"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsNoSavings and investments on 1 January, euros. Default 0.
partnerNoHas an allowance partner. Default false.
gross_annualYesGross annual salary, euros (10000-100000)
monthly_rentNoMonthly rent for rent allowance, 0 if owning. Default 0.
children_agesNoAges of children under 18. Default none.
partner_incomeNoThe partner's yearly income, euros. Default 0.

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?

The annotations already declare the tool as read-only, idempotent, non-destructive and closed-world, so the safety profile is clear. The description adds meaningful behavioral context by explaining that it computes allowance loss alongside extra income tax and identifies cliff ranges, although it does not state computational assumptions or caveats.

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 two tightly written sentences that front-load the 2026 salary context and then enumerate the main outputs. Every clause contributes to understanding what the tool returns.

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 carries the burden of explaining return values, and it does so by naming allowances, net income including allowances, the kept share of the next €1,000, and cliff salary ranges. It is largely complete for invoking the tool, though additional output-structure detail or assumptions would strengthen it further.

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 all six parameters are already documented in the input schema. The description reinforces household allowance concepts such as rent allowance, healthcare allowance, and child budget, but adds little syntax or format detail 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 states a specific calculation for the Netherlands in 2026: allowances, net income, the share of the next €1,000 kept, and salary ranges where raises are mostly lost. This clearly distinguishes it from a plain net-salary or benefits calculator, though it does not explicitly name sibling alternatives.

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?

Use is implied by the phrase 'For a salary in the Netherlands in 2026' and by the mention of salary ranges where a raise is mostly lost. However, there is no explicit guidance on when to choose this tool over siblings such as benefits_toeslagen_check or net_salary_netherlands.

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