Skip to main content
Glama

Saat farkı

saat_farki_hesapla
Read-onlyIdempotent

İki saat arasındaki süreyi mola düşerek saat, dakika ve ondalık saat olarak hesaplar. Bitiş başlangıçtan küçük ya da eşitse gece yarısı geçilmiş sayılır.

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>",
      "bitis": "<bitis>"
    },
    "name": "saat_farki_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitisYesÖr. 18:30.
baslangicYesÖr. 09:00.
molaDakikaNoMola (dakika). Varsayılan 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / baslangic / description
      Previous value: -"Başlangıç saati, SS:DD (24 saat), ör. 09:00."New value: +"Ör. 09:00."
    • changedInput schema / properties / bitis / description
      Previous value: -"Bitiş saati, SS:DD (24 saat), ör. 18:30."New value: +"Ör. 18:30."
    • changedInput schema / properties / molaDakika / description
      Previous value: -"Düşülecek mola, dakika. Varsayılan 0."New value: +"Mola (dakika). Varsayılan 0."
  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 and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the break deduction and the explicit rule that end <= start is treated as crossing midnight, which an agent could not infer from structured fields.

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 sentences, zero filler. The primary behavior comes first and the midnight-crossing rule, the one non-obvious case, follows immediately.

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 usefully names the three output representations (hours, minutes, decimal hours). The midnight rule closes the main ambiguity. Minor gaps remain, such as whether the result is capped at 24 hours or how break times exceeding the span are handled.

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%, so both time parameters and the break parameter are already documented with patterns and examples. The description only reinforces that the break is subtracted and gives the output units; it adds no formatting or edge-case detail beyond the schema.

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 states a specific verb and resource: it computes the elapsed time between two clock times, deducting a break, and returns hours, minutes and decimal hours. The 'iki saat arasındaki' framing makes it distinguishable from a date-difference tool, but it never names or contrasts a sibling explicitly.

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 by the resource (two time-of-day values), so an agent can infer it is for same-day or overnight shift spans. There is no explicit when-to-use / when-not guidance and no pointer to the date-difference alternative for multi-day spans.

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