Skip to main content
Glama

Asgari ücret zammı

asgari_ucret_zammi_hesapla
Read-onlyIdempotent

Verilen zam oranıyla yeni brüt ve net asgari ücreti hesaplar (senaryo).

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": {
      "zamOrani": "<zamOrani>"
    },
    "name": "asgari_ucret_zammi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
zamOraniYesBrüte zam (%).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / zamOrani / description
      Previous value: -"Brüt asgari ücrete uygulanacak zam oranı (%)."New value: +"Brüte zam (%)."
  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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the output covers both gross and net and that this is a scenario computation, but says nothing about the base wage, tax bracket or other assumptions used to derive the net figure — the main behavioral unknown for a wage calculator.

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?

A single short sentence with the outcome (new gross and net minimum wage) front-loaded and zero filler. Nothing in it is redundant with the schema.

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 one-parameter, read-only computation with full schema coverage and annotations, the description is nearly sufficient: it names both output values and frames the tool as a scenario. The only gap is the underlying assumptions (base wage, tax treatment) an agent would want when explaining the result, though no output schema exists to cover that.

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% and the single parameter is documented as "Brüte zam (%)" with a 0–200 range. The description's phrase "verilen zam oranıyla" merely restates the parameter without adding interpretation such as whether the percentage applies to the gross figure only. Baseline 3 applies when the schema carries the semantics.

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 verb and resource: it calculates ("hesaplar") the new gross and net minimum wage from a given raise rate, and flags the context as a scenario. It is distinguishable from wage-adjacent siblings such as brut_net_maas_hesapla by naming minimum wage explicitly, though it does not call out any alternative by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance. The parenthetical "(senaryo)" hints that this is a hypothetical/what-if calculation rather than an official payroll figure, but the agent must infer whether to prefer this over memur_emekli_zammi_hesapla or brut_net_maas_hesapla.

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