Skip to main content
Glama

İşveren maliyeti

isveren_maliyeti_hesapla
Read-onlyIdempotent

Brüt maaştan işverenin toplam maliyetini (SGK ve işsizlik işveren payı, prim indirimi, asgari ücret desteği) ve çalışanın netini hesaplar.

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": {
      "brutMaas": "<brutMaas>"
    },
    "name": "isveren_maliyeti_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
brutMaasYesAylık brüt maaş (TL).
primIndirimiNodiger: imalat dışı. Varsayılan diger.
asgariUcretDestegiNoVarsayılan false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / asgariUcretDestegi / description
      Previous value: -"Asgari ücret desteğinden yararlanılıyor mu? Varsayılan false."New value: +"Varsayılan false."
    • changedInput schema / properties / primIndirimi / description
      Previous value: -"SGK işveren prim indirimi: imalat, diger (imalat dışı) ya da yok. Varsayılan diger."New value: +"diger: imalat dışı. Varsayılan diger."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description only needs to add context. It does add the useful framing that this is a pure computation from gross salary, but it omits a significant behavioral trait: no year/period parameter exists, so the agent is never told which statutory rates or year's parameters are assumed.

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?

A single front-loaded sentence with the verb, source input, and computed outputs in a logical order; no filler. It could be marginally clearer by naming the returned quantities separately, but nothing is wasted.

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

Completeness3/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 bears responsibility for indicating what comes back; it partially does so by naming the computed cost components and the employee net. But it never states the return structure (separate fields vs. single total), currency, or the statutory assumptions, which matters for a financial calculator.

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 all three parameters (brutMaas, primIndirimi enum, asgariUcretDestegi) are already documented in the schema, making a baseline of 3 appropriate. The description's parenthetical about 'prim indirimi' and 'asgari ücret desteği' loosely maps to the optional parameters but adds no format, default, or enum semantics beyond what the schema already states.

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?

The description names a concrete verb ('hesaplar') and a concrete resource (employer total cost from gross salary), and enumerates the cost components (SGK and unemployment employer share, premium discount, minimum wage support) plus the employee net. It is clearly distinguishable from most siblings, though the overlap with brut_net_maas_hesapla on 'net' is not explicitly resolved.

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 input ('Brüt maaştan' — starting from gross salary), which tells the agent the expected input direction. However, there is no explicit when-to-use statement, no mention of when to prefer brut_net_maas_hesapla or isten_ayrilma_alacaklari_hesapla, and no stated preconditions.

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