EOR Scope

Employer cost of an employee in a country

employer_cost

Read-only

Use this when the user asks what an employee costs the employer in a country beyond the gross salary: employer social security contributions, payroll taxes, pension, health or accident insurance, mandatory levies, or the total cost of employment (e.g. "how much does it cost to employ a developer in Germany at 80k", "employer charges in Spain", "coût employeur d'un salarié en Pologne"). Returns each statutory employer contribution with its rate, base, ceiling, source (official wherever one exists) and check date, then the monthly and annual total and its percent of gross, before any Employer of Record fee. A total the country declares as a floor or a ceiling is written "at least" or "at most". A monthly salary is passed as the user gives it, with salary_period "month": the country's statutory 13th or 14th month is then applied (e.g. "a hire at 4,000 a month in Madrid", "un salarié payé 2 500 par mois à Lisbonne"). Do not use for an employee's net pay or income tax, for legal advice, or for the fees of a provider. Amounts given in the local currency come back in it, with the USD in brackets. Data snapshot 2026-10-22. Cost comparison, not legal or tax advice.

Input Schema

Name	Required	Description	Default
`salary`	No	Gross salary, a year unless salary_period is "month". Omit to use the country's example salary.
`country`	Yes	ISO 3166-1 alpha-2 code ("DE") or country name ("Germany")
`assumptions`	No	Override an adjustable assumption the country declares, e.g. {"basic_share_of_gross": 0.6}. See `assumptions` in an employer_cost answer.
`include_notes`	No	Include the long legal note behind each line
`salary_period`	No	Whether the salary is a year (default) or a month. Pass a monthly salary as the user gives it, with "month": the statutory number of monthly payments of the country (13th, 14th month) is applied, see salary_basis in the answer.	year
`salary_currency`	No	Currency of `salary`: USD, or the local currency of the country	USD
`payments_per_year`	No	With salary_period "month" only: the total number of monthly salaries the contract pays in a year, statutory ones included (e.g. 14). Omit to use the statutory number of the country.

Output Schema

Name	Required	Description	Default
`meta`	Yes
`lines`	Yes
`salary`	Yes
`widget`	No
`country`	Yes
`summary`	Yes
`assumptions`	Yes
`not_in_total`	Yes
`salary_basis`	No
`employer_cost`	Yes
`included_in_gross_salary`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already establish readOnly and non-destructive behavior, and the description adds substantial context: per-contribution rates, bases, ceilings, sources, check dates, totals, floor/ceiling wording, local-currency return with USD in brackets, and the data snapshot date. It also discloses the 13th/14th month treatment and that results exclude Employer of Record fees.

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?

The description is long but front-loaded and logically ordered: purpose, output contents, special-case rules, exclusions, and data caveats. The multiple parenthetical example queries add some bulk, but every sentence carries useful routing or behavioral information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given seven parameters, a nested assumptions object, and an output schema, the description is complete enough for correct invocation. It covers the calculation basis, currency behavior, unusual salary period handling, total-cost definitions, and the important disclaimer that this is a cost comparison rather than legal or tax advice.

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 usefully reinforces salary_period semantics: monthly salaries are passed as given and the country's statutory extra months are applied. It also gives a concrete assumptions override example, though much of the remaining parameter detail is already in the schema.

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 and resource: computes the employer-side cost of an employee in a country, including social security, payroll taxes, pension, insurance, and levies. It clearly distinguishes itself from siblings like compare_countries and max_salary_for_budget by focusing on a single country's statutory employer burden.

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?

Gives explicit when-to-use cues with concrete example queries in multiple languages, plus strong exclusions: not for net pay, income tax, legal advice, or provider fees. It does not explicitly route the agent to a named sibling for related alternative tasks, which keeps it just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All EOR Scope tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.