Skip to main content
Glama

İş günü

is_gunu_hesapla
Read-onlyIdempotent

İki tarih arasındaki iş günü sayısı: hafta sonları ve resmî tatiller düşülür, arifeler yarım gün, iki uç dahil.

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

Input Schema

NameRequiredDescriptionDefault
bitisYes
baslangicNoBoşsa bugün.
cumartesiCalisilirNoCumartesi iş günü mü. Varsayılan false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / baslangic / description
      Previous value: -"Başlangıç tarihi, YYYY-AA-GG. Boş bırakılırsa bugün (Türkiye)."New value: +"Boşsa bugün."
    • removedInput schema / properties / bitis / description
      Removed value: -"Bitiş tarihi, YYYY-AA-GG."
    • changedInput schema / properties / cumartesiCalisilir / description
      Previous value: -"true ise Cumartesi iş günü sayılır (resmî tatile denk gelen Cumartesi yine sayılmaz). Varsayılan false."New value: +"Cumartesi iş günü mü. Varsayılan false."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description does add real behavioral content beyond that — weekend/holiday subtraction, half-day eves, inclusive endpoints — but leaves two things unstated that materially change results: which holiday calendar is assumed (presumably Turkish official holidays) and whether half-day eves can produce fractional returns.

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 front-loaded sentence that packs the purpose and all calculation rules with zero filler. Every clause (weekends, holidays, eve half-days, inclusive endpoints) carries load-bearing information.

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 three-parameter calculator with no output schema, the description covers the core calculation semantics well. The remaining gaps — return format (integer vs. .5 increments) and the holiday calendar source — are minor but real for a tool whose whole value is a precise number.

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 coverage is 67% and the schema itself documents baslangic (defaults to today) and cumartesiCalisilir (defaults false). The description adds one genuinely useful semantic — 'iki uç dahil', i.e. both endpoints count — but never mentions the cumartesiCalisilir switch, which directly alters the count, nor clarifies what an omitted baslangic means.

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?

States a specific verb+resource: counting business days (iş günü) between two dates. The exclusion rules (weekends, official holidays) implicitly separate it from generic date-difference siblings like gun_sayaci_hesapla or tarih_farki_hesapla, but no sibling is named outright, so differentiation is inferential rather than explicit.

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?

No explicit when-to-use / when-not-to-use statement and no pointer to an alternative tool. Usage is only implied by the domain wording (business days with holiday exclusion), which a caller can read as 'use this instead of a plain day counter' but must infer on their own.

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