Skip to main content
Glama

Brüt-net maaş

brut_net_maas_hesapla
Read-onlyIdempotent

Türkiye maaşı: brütten neti ya da netten brütü güncel SGK, işsizlik sigortası, gelir vergisi dilimleri, damga vergisi ve asgari ücret istisnasıyla hesaplar. Ocak ayı esas alınır; yıl sonu neti de verilir.

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": {
      "tutar": "<tutar>"
    },
    "name": "brut_net_maas_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
yonNoVarsayılan brutten-nete.
tutarYesAylık tutar (TL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / yon / description
      Previous value: -"brutten-nete (tutar brüttür) ya da netten-brute (tutar nettir). Varsayılan brutten-nete."New value: +"Varsayılan brutten-nete."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description's added value is in methodology: it enumerates the statutory components applied (SGK, unemployment insurance, income tax brackets, stamp tax, minimum wage exemption) and the January-basis assumption. That is real behavioral context beyond the structured fields; it only stops short of stating which year's rates are used despite the word 'güncel'.

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?

Two dense sentences: the first front-loads the domain and both conversion directions, the second front-loads the calculation basis and the extra year-end figure. Nothing is redundant and no sentence is filler.

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 must hint at returns, and it does by noting that the year-end net figure is also provided, alongside the statutory components used. For a two-parameter calculation tool this is nearly complete; only the rate year and rounding conventions remain unstated.

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%, with both parameters documented and the direction enum self-explanatory, so the schema carries the parameter burden. The description echoes the direction choice and adds that results rest on a January basis, but contributes no format, rounding, or unit detail beyond what the schema already says.

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 names a specific verb ('hesaplar') and resource (Turkish salary) and explicitly covers both directions ('brütten neti ya da netten brütü'), which separates it from siblings like isveren_maliyeti_hesapla or fazla_mesai_hesapla that touch salary-adjacent numbers but answer different questions.

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?

Usage is implied by the domain framing: an agent can infer this is the tool for gross-to-net or net-to-gross salary conversion. However, it never states when to prefer it over adjacent tools (employer cost, overtime, severance, unemployment benefit) or any prerequisites such as the applicable tax year, so routing guidance is left to inference.

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