Skip to main content
Glama
TurkActuary MCP

TurkActuary MCP

by afsharid

asgari_ucret

Read-onlyIdempotent

Fetches Türkiye's monthly minimum wage by date range, returning gross and net amounts and an AGI option for pre-2022 periods. Output periods can feed compensation calculations directly.

Instructions

Türkiye aylık asgari ücreti (16 yaş üstü; ÇSGB tabloları, 2008–2026): tarih aralığındaki dönemler, brüt ve net. Çıktıdaki gelir_donemleri tazminat araçlarına doğrudan verilebilir. 2022 öncesi için agi_dahil seçilmelidir (asgari geçim indirimi; kararlarda açık kural yok).

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": {
      "baslangic": "<baslangic>"
    },
    "name": "asgari_ucret"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitisNoYYYY-AA-GG, dahil değil; verilmezse tek gün
agi_dahilNo2022 öncesi dönemlerde AGİ eklenmiş net mi
baslangicYesYYYY-AA-GG

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description still adds useful context: the source (ÇSGB tables), the coverage window 2008–2026, the 16+ age restriction, and the fact that both gross and net are returned. It says nothing about response shape beyond the gelir_donemleri field name, and there is no output schema, so that gap is not fully closed.

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?

Three tight clauses with no filler: scope and source first, then the downstream-consumption note, then the parameter caveat. The parentheticals are dense but each carries real information. Slightly loaded, but nothing is redundant.

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 three-parameter read with no output schema, the definition covers source, temporal coverage, age scope, returned fields, and the one genuinely ambiguous parameter choice. Remaining unknowns are minor, namely the exact list of fields per period and whether periods are truncated at range boundaries. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above baseline by turning the agi_dahil parameter from a bare flag into a normative instruction tied to the pre-2022 boundary and flagging that jurisprudence is silent on it. It also characterizes the date arguments as defining a period range rather than a single date, which the bitis schema text only partially conveys.

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?

Names a specific resource and scope: Turkish monthly minimum wage, 16+, sourced from ÇSGB tables, covering 2008–2026, returning periods within a date range as gross and net. The verb 'retrieves/returns' is implied by 'tarih aralığındaki dönemler, brüt ve net'. It does not name a sibling, but the note that gelir_donemleri feeds compensation tools implicitly separates it from the valuation/modeling siblings.

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?

Gives a concrete conditional rule: for periods before 2022, agi_dahil must be selected, with the caveat that court decisions contain no explicit rule. It also states the intended downstream use (feeding compensation tools). No explicit when-not-to-use or named alternative is given, so it stops short of a 5.

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