Skip to main content
Glama

Askerlik terhis tarihi

askerlik_terhis_tarihi_hesapla
Read-onlyIdempotent

Askerlik sevk tarihinden terhis tarihini, kalan günü (şafak) ve tamamlanan yüzdeyi hesaplar. Süreler (7179 s. Kanun): er/erbaş 6 ay, yedek subay 12 ay, yedek astsubay 12 ay, bedelli (temel eğitim) 1 ay.

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": {
      "sevkTarihi": "<sevkTarihi>"
    },
    "name": "askerlik_terhis_tarihi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
turNoVarsayılan er (er/erbaş).
sevkTarihiYesBirliğe sevk (katılış) tarihi.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / sevkTarihi / description
      Previous value: -"Birliğe sevk (katılış) tarihi, YYYY-AA-GG."New value: +"Birliğe sevk (katılış) tarihi."
    • changedInput schema / properties / tur / description
      Previous value: -"Hizmet türü: er (er/erbaş), yedekSubay, yedekAstsubay, bedelli. Varsayılan er."New value: +"Varsayılan er (er/erbaş)."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so safety is covered. The description adds substantive context beyond that: the statutory basis (7179 sayılı Kanun) and the fixed service durations per status, which tells the agent how the result is derived rather than just that it is a pure read. It stops short of describing output shape, but that is a minor gap for a deterministic 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?

Two compact sentences with zero filler: the first front-loads what is computed, the second supplies the legal duration table. Every clause carries information the caller needs.

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 two-parameter, no-output-schema calculator the definition is nearly complete: inputs, status variants, and resulting outputs are all identified. The only missing piece is how partial months or edge dates are handled, which an agent might want before relying on the exact şafak figure.

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 baseline is 3, and the description earns above that by explaining what each tur value means in duration terms (er/erbaş 6 months, yedek subay/yedek astsubay 12 months, bedelli 1 month). That mapping is not derivable from the enum identifiers alone and lets the agent pick the right enum value and predict the outcome.

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?

States a specific verb (hesaplar) plus the exact resource (askerlik sevk tarihinden terhis tarihi) and even enumerates the three computed outputs: discharge date, remaining days (şafak), and completion percentage. Among date-oriented siblings like tarih_farki_hesapla or gun_sayaci_hesapla, this is unmistakably the military-service variant.

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 rather than stated: an agent can infer it should call this when it has a sevk (enlistment) date and needs a discharge timeline. There is no explicit when-not guidance, no mention of alternatives such as the generic date-difference tool, and no prerequisites called out.

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