Skip to main content
Glama

Turkey Salary and Income Tax Calculator

Employer cost of a salary in Turkey

employer_cost
Read-onlyIdempotent

What a salary in Turkey costs the employer (employer social contributions itemised), or the reverse: the gross salary a total budget allows. Give gross_annual or budget_annual.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "employer_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
besNoPrivate pension auto-enrolment (BES, 3%) Default false.
tax_yearNoTax year. Offered: 2026 (final), 2025 (final). Default 2026. A year that is not listed is not available for this country.
incentiveNoEmployer SGK incentive: 2 = 2 points (most sectors, 2026); 5 = 5 points (manufacturing); 0 = None. Default 2.
fx_per_eurNoExchange rate: 1 euro = this many TRY, for the euro amounts. Default 38 (indicative).
bonus_annualNoYearly bonus in TRY. Default 0.
gross_annualNoGross yearly salary in TRY
budget_annualNoTotal yearly employer budget in TRY, to find the gross salary it allows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tax_year
      Added value: +{
      +  "description": "Tax year. Offered: 2026 (final), 2025 (final). Default 2026. A year that is not listed is not available for this country.",
      +  "enum": [
      +    2026,
      +    2025
      +  ],
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavior: contributions are itemised and the tool can invert the calculation. It stops short of saying whether the two amount parameters are mutually exclusive or what error results if both are given.

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?

Two short sentences with the core purpose front-loaded, followed immediately by the calling instruction. No filler, though the reverse mode is packed into the same sentence rather than separated.

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 7-parameter, zero-required calculator with full schema descriptions and read-only annotations, the description covers both modes and the key input rule. The only gap is the missing explanation of mutual exclusivity and edge cases when neither amount is passed.

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 coverage is 100%, so every parameter including enums and defaults is already documented in structured form. The description only names gross_annual and budget_annual and implies one should be supplied, which the schema does not express as a oneOf constraint — a small but real addition beyond the schema. Baseline 3 is appropriate given the schema does the heavy lifting.

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?

States a concrete verb-plus-resource: it computes employer cost of a Turkish salary with itemised social contributions, and also runs in reverse to derive the gross salary a budget permits. That is far more specific than the title alone. It does not, however, distinguish itself from siblings such as gross_for_target_net, which the reverse mode superficially resembles.

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?

"Give gross_annual or budget_annual" explicitly tells the agent how to pick the direction of the calculation, which is the main usage decision for this tool. There is no guidance on what happens if both or neither are supplied, and no naming of alternatives for related net-based questions.

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