Skip to main content
Glama

Compare Dutch job offers after tax

job_offer_comparison
Read-onlyIdempotent

Compares two or three Dutch job offers by what is left after income tax in 2026: base salary, 8% holiday allowance, the 30% ruling (with its salary norm), the employee pension contribution and a bonus. Returns net per year and per month for each and the difference.

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": {
      "offers": "<offers>"
    },
    "name": "job_offer_comparison"
  }
}

Input Schema

NameRequiredDescriptionDefault
offersYesThe offers to compare

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive calculation. The description adds useful behavioral context: the 2026 tax year, the 30% ruling salary norm, the included compensation components, and the net yearly/monthly output plus difference.

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 dense sentence with the main purpose and output front-loaded. Every clause contributes either scope, input meaning, or return format.

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 appropriately explains that results are net per year, net per month, and the difference. It is nearly complete for a calculator tool, though it does not discuss assumptions, rounding, or edge cases around the 30% ruling.

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 detailed field descriptions already do most of the work. The tool description still adds meaning by mapping the calculation to base salary, 8% holiday allowance, 30% ruling with salary norm, pension contribution, and bonus, and by clarifying the two-or-three offer comparison scope.

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 states a specific verb and resource: it compares two or three Dutch job offers after income tax in 2026. It also names the exact components considered and distinguishes the tool from single-salary net calculators by focusing on multi-offer comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context is clear: use this for comparing two or three Dutch job offers after tax. It does not explicitly mention when not to use it or name sibling alternatives such as single-salary net calculation or country comparison, so it stops short of full routing guidance.

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