Skip to main content
Glama

Gün sayacı

gun_sayaci_hesapla
Read-onlyIdempotent

Hedef tarihe kaç takvim günü kaldığını (geçtiyse kaç gün geçtiğini) hafta dökümüyle hesaplar; tatiller düşülmez.

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": {
      "hedefTarih": "<hedefTarih>"
    },
    "name": "gun_sayaci_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
hedefTarihYesÖr. 2027-06-19.
referansTarihNoBoşsa bugün.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / hedefTarih / description
      Previous value: -"Hedef tarih, YYYY-AA-GG biçiminde (ör. 2027-06-19)."New value: +"Ör. 2027-06-19."
    • changedInput schema / properties / referansTarih / description
      Previous value: -"Hangi güne göre sayılacağı, YYYY-AA-GG. Boş bırakılırsa bugün (Türkiye)."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, closed-world and non-destructive, so the safety profile is covered. The description still adds real value beyond that: holidays are NOT deducted, past dates yield elapsed days rather than an error, and the response carries a per-week breakdown. Only the exact return shape is left unstated.

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?

One compact sentence that front-loads the core result and then qualifies it with the past-date case, the week breakdown, and the holiday caveat. No redundant restatement of the title or name.

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, closed-world, read-only calculation with a fully documented schema and no output schema, the description covers what is computed, the edge case of past dates, and the notable exclusion of holidays. An agent could invoke it correctly, with only minor detail about the response left unspecified.

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%, with each parameter documented and an ISO date example given, so the schema does the heavy lifting. The description adds no syntax or format guidance for hedefTarih or referansTarih beyond what is already structured; baseline 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 names a specific computation (calendar days until a target date), covers the reverse case (elapsed days if the date has passed), and adds the 'hafta dökümü' week breakdown. The clause 'tatiller düşülmez' implicitly sets it apart from the business-day calculator sibling, though it never names that alternative directly.

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: the holiday-exclusion note tells an agent this is for pure calendar counting, which hints that is_gunu_hesapla is the right tool when working days are needed. There is no explicit when-to-use or when-not-to-use statement and no named alternative.

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