Skip to main content
Glama

Yaş

yas_hesapla
Read-onlyIdempotent

Doğum tarihinden yaşı (yıl, ay, gün), yaşanan toplam günü ve sonraki doğum gününe kalan günü 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": {
      "dogumTarihi": "<dogumTarihi>"
    },
    "name": "yas_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
dogumTarihiYesDoğum tarihi.
referansTarihNoBoşsa bugün.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / dogumTarihi / description
      Previous value: -"Doğum tarihi, YYYY-AA-GG."New value: +"Doğum tarihi."
    • changedInput schema / properties / referansTarih / description
      Previous value: -"Hangi tarihteki yaş, YYYY-AA-GG. Boşsa bugün."New value: +"Boşsa bugün."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds real value beyond that by disclosing the exact computed outputs (yıl/ay/gün breakdown, total days, days until next birthday), which is important since no output schema exists.

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 sentence with zero filler, front-loading the input (doğum tarihi) and then the three results. Nothing is repeated and nothing unrelated is included.

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 simple two-parameter, fully documented, annotated read-only tool with no output schema, the description supplies exactly the missing piece: what is returned. Only a note on how the reference date affects results would make it fully self-contained, and that is already in the schema.

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%: both dogumTarihi and referansTarih carry their own descriptions and date patterns, including that an empty referansTarih means today. The description adds no format or default detail beyond the schema, so the baseline of 3 applies.

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 gives a specific verb (hesaplar) and resource (yaş) and enumerates the three outputs: age in years/months/days, total days lived, and days to next birthday. It is clear what the tool does, but it never distinguishes itself from adjacent siblings such as tarih_farki_hesapla or gun_sayaci_hesapla, which an agent may see as overlapping.

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 only implied by the stated purpose: an agent can infer it is the right tool when it needs someone's age. There is no explicit when-to-use statement, no prerequisite, and no pointer to an alternative for the neighbouring date-difference or day-count cases.

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