Turkey Salary Calculator

Gross salary needed for a net amount in Turkey

gross_for_target_net

Read-onlyIdempotent

The gross yearly salary in Turkey that leaves a given take-home pay, with the same situation options as net_salary. Use it to set a salary ask or check an offer.

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": {
      "net_target": "<net_target>"
    },
    "name": "gross_for_target_net"
  }
}

Input Schema

Name	Required	Description
`bes`	No	Private pension auto-enrolment (BES, 3%) Default false.
`period`	No	Whether net_target is per year or per month. Default year.
`incentive`	No	Employer SGK incentive: 2 = 2 points (most sectors, 2026); 5 = 5 points (manufacturing); 0 = None. Default 2.
`fx_per_eur`	No	Exchange rate: 1 euro = this many TRY, for the euro amounts. Default 38 (indicative).
`net_target`	Yes	Take-home pay wanted, in TRY
`bonus_annual`	No	Yearly bonus in TRY. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.5/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 fully covered. The description confirms the tool is a Turkish take-home inversion and that its options mirror net_salary, but says nothing about rounding, assumptions in the calculation, or that euro-denominated figures may be returned via fx_per_eur.

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, front-loaded with the core definition before the use case. The phrasing 'that leaves a given take-home pay' is slightly indirect but nothing is wasted.

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 six fully documented parameters, no output schema and complete annotations, the description covers what an agent needs to select and call the tool. The remaining gap is the mismatch between 'gross yearly salary' and the monthly period option, which could mislead an agent about the returned unit.

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 every parameter, enum and default is already documented in the schema. The description's only added semantic is 'same situation options as net_salary', which usefully signals parameter parity with a sibling but adds no detail beyond that.

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 specific computation (gross salary that yields a given net take-home) scoped to Turkey, and anchors it to the sibling net_salary as its inverse. The only weakness is that it says 'gross yearly' while the period parameter also permits monthly, a small imprecision in an otherwise clear purpose statement.

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?

Offers two concrete usage contexts ('set a salary ask or check an offer') and points at net_salary for the mirrored option set, which is genuinely helpful. However, it never states when to prefer net_salary's forward direction instead, nor any exclusions, so routing is only implied.

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

All Turkey Salary Calculator 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.

Resources

Need Help?