Skip to main content
Glama

Tarih farkı

tarih_farki_hesapla
Read-onlyIdempotent

İki tarih arasındaki farkı yıl, ay, gün ve toplam gün/hafta/ay olarak hesaplar (takvim günü, tatiller düşülmez). baslangic ve bitis tarihlerinden EN AZ BİRİ verilmelidir; verilmeyen bugün sayılır.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tarih_farki_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitisNoBoşsa bugün.
baslangicNoBoşsa bugün.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / baslangic / description
      Previous value: -"Başlangıç tarihi, YYYY-AA-GG. Verilmezse bugün (bitis verilmişse)."New value: +"Boşsa bugün."
    • changedInput schema / properties / bitis / description
      Previous value: -"Bitiş tarihi, YYYY-AA-GG. Verilmezse bugün (baslangic verilmişse)."New value: +"Boşsa bugün."
  2. Changed2 schema fields changed
    • changedInput schema / properties / baslangic / description
      Previous value: -"Başlangıç tarihi, YYYY-AA-GG. Boşsa bugün."New value: +"Başlangıç tarihi, YYYY-AA-GG. Verilmezse bugün (bitis verilmişse)."
    • changedInput schema / properties / bitis / description
      Previous value: -"Bitiş tarihi, YYYY-AA-GG. Boşsa bugün."New value: +"Bitiş tarihi, YYYY-AA-GG. Verilmezse bugün (baslangic verilmişse)."
  3. First observed

TDQS

A3.9/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, so the safety profile is covered. The description adds genuine behavioral detail beyond them: results are calendar-based with holidays NOT deducted, and missing dates fall back to today. It does not state what happens if bitis precedes baslangic, so it stops short of a 5.

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 tight sentences with no filler: first the operation and output units, then the input constraint and default. The most important constraint is capitalized and placed where it will be read.

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?

With no output schema, the description carries the return-value burden and does so by listing the computed units. For a two-parameter calculator with full annotations, the only real gap is unstated behavior for reversed or equal dates.

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, but the description earns more by declaring a constraint the schema omits: 'baslangic ve bitis tarihlerinden EN AZ BİRİ verilmelidir', which the empty required array does not convey. The default-to-today behavior restates the schema's own parameter descriptions rather than adding new information.

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 opens with a specific verb ('hesaplar') and resource ('İki tarih arasındaki fark') and enumerates the output units (yıl, ay, gün ve toplam gün/hafta/ay). The parenthetical 'takvim günü, tatiller düşülmez' implicitly separates it from business-day siblings like is_gunu_hesapla, though no sibling is named outright.

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 context is implied by the scope (date-difference math) and the default-to-today rule, but there is no explicit when-to-use statement or named alternative such as gun_sayaci_hesapla or is_gunu_hesapla. The caller must infer the boundary from the 'tatiller düşülmez' note alone.

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