Skip to main content
Glama

Highly skilled migrant / EU Blue Card salary check

visa_salary_check
Read-onlyIdempotent

Checks whether a salary meets the 2026 IND salary requirement for a Dutch highly skilled migrant (kennismigrant) permit or an EU Blue Card. Holiday allowance does not count; a 13th month counts only when paid monthly. Also checks the 30% ruling salary norm.

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": {
      "salary": "<salary>"
    },
    "name": "visa_salary_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
perNoWhether salary is per year or per month. Default year.
permitNohsm = highly skilled migrant, bluecard = EU Blue Card. Default hsm.
salaryYesGross salary in euros, as in the offer
under_30NoApplicant is under 30 on the day the application is filed. Default false.
recent_graduateNoGraduated within the last 3 years or on an orientation-year permit (reduced norm). Default false.
thirteenth_monthNoA 13th month: none, paid as a lump sum (does not count), or paid in 12 monthly parts (counts). Default none.
includes_holiday_payNoThe salary amount includes the 8% holiday allowance. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine behavioral context beyond that: holiday allowance is excluded and a 13th month only counts when paid monthly, which materially affects results. It still omits what the response looks like or how borderline cases are reported.

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?

Three short sentences, front-loaded with the core purpose, then the two counting rules. Every sentence earns its place and nothing is padded.

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 read-only single-value check with seven well-documented parameters and full schema coverage, the description is nearly complete. The one gap is that there is no output schema and the description does not say what the result contains (pass/fail, which threshold, applicable amount), though the verb 'checks whether' implies a verdict.

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 description coverage is 100%, so the baseline is 3. The description adds interpretive meaning beyond the schema by stating that holiday allowance does not count toward the norm, clarifying how includes_holiday_pay and thirteenth_month interact with the threshold rather than merely restating the field definitions.

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?

States a specific verb (checks) plus resource (IND 2026 salary requirement for kennismigrant / EU Blue Card) and names the third norm covered (30% ruling). It is immediately distinguishable from siblings like net_salary_netherlands, which computes net pay rather than testing a threshold.

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 description scopes usage clearly: it covers three specific norms (HSM, EU Blue Card, 30% ruling) for 2026, which tells an agent when this tool applies. It does not, however, name alternatives or state when-not to use it (e.g. vs net_salary_netherlands for take-home pay).

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