Skip to main content
Glama

Yaklaşan önemli günler

yaklasan_onemli_gunler
Read-onlyIdempotent

Yaklaşan resmî tatil, bayram, dinî gün, sınav (ÖSYM, MEB), okul takvimi ve vergi son günlerini kalan günle listeler.

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": "yaklasan_onemli_gunler"
  }
}

Input Schema

NameRequiredDescriptionDefault
enFazlaNoSatır sayısı. Varsayılan 15.
kategoriNoVarsayılan hepsi.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / enFazla / description
      Previous value: -"En fazla kaç satır dönsün. Varsayılan 15."New value: +"Satır sayısı. Varsayılan 15."
    • changedInput schema / properties / kategori / description
      Previous value: -"Süzgeç: tatil = Resmî tatiller ve bayramlar; dini = Dinî günler; sinav = Sınavlar; okul = Okul takvimi; ekonomi = Ekonomik tarihler. Varsayılan hepsi."New value: +"Varsayılan hepsi."
  2. First observed

TDQS

B3.4/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 the safety profile is covered and the description only needs to add context. It does add that each row carries the remaining number of days, which is genuinely useful. However, it does not disclose the forward horizon covered by "upcoming" or the ordering of results — the main behavioral unknown for a date-list tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that enumerates categories without filler, so nothing is wasted. It is well sized for the tool, though splitting off a short clause about how far ahead it looks would improve it without adding bulk.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with two optional parameters and no output schema, the description tells the agent what is returned and in what form (entries with days remaining). The key omission is the definition of "upcoming" — no horizon, no ordering, and no mention of the default 15 rows, which the agent would need to interpret or report results.

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 the default value and the meaning of enFazla and that of the kategori enum are documented in the schema itself. The description adds nothing about the parameters, so the baseline 3 applies — the schema carries all parameter meaning.

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 verb ("listeler") and enumerates what is listed: official holidays, bayram, religious days, exams (ÖSYM, MEB), school calendar and tax deadlines. That makes the tool's scope instantly distinguishable from the sibling calculators, though it does not explicitly contrast itself with any of them.

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: an agent can infer it should call this for upcoming-date questions, since all sibling tools are one-off calculations. There is no explicit statement of when to prefer this tool, and no exclusion or note about what it cannot answer (for example historic dates).

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