Skip to main content
Glama

Namaz vakitleri

takvim_get_prayer_times

Retrieve Islamic prayer times for any Turkish province or district from Diyanet data, including imsak, sunrise, and daily prayer schedules for upcoming days.

Instructions

Islamic prayer times (namaz vakitleri, ezan, iftar/sahur) for any Turkish province/district from Diyanet data: imsak, güneş, öğle, ikindi, akşam, yatsı. Uses the official Diyanet API if DIYANET_EMAIL/DIYANET_PASSWORD are set, otherwise a keyless Diyanet mirror.

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": {
      "il": "<il>"
    },
    "name": "takvim_get_prayer_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
ilYesİl
ilceNoİlçe. Boşsa il merkezi.
gunSayisiNoBugünden itibaren kaç gün (1–30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose a genuinely useful behavior: two possible backends with an env-var-driven switch and a keyless mirror fallback. It omits return format, error behavior for unknown il/ilce, and any rate-limit characteristics, which keeps it 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.

Conciseness4/5

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

A single dense sentence front-loads the resource and the synonym set (namaz vakitleri, ezan, iftar/sahur) that aids retrieval, then the backend note. Nothing is wasted, though it is packed tight enough that the auth clause could read as a run-on.

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 three-parameter read tool with a fully documented schema and no output schema, the description supplies enough to call it correctly: scope, fields, data source and backend behavior. The main untold piece is how locality names are matched and what happens on an unmatched province.

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 100%, so il, ilce and gunSayisi are already documented in the schema. The description corroborates that coverage spans provinces and districts but adds no format, matching, or date-window semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (Islamic prayer times for Turkish provinces/districts), enumerates the exact fields returned (imsak, güneş, öğle, ikindi, akşam, yatsı), and names the data source (Diyanet), which cleanly separates it from takvim_get_holidays and the other takvim/izmir siblings.

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 rather than stated: the description tells you what data it serves but never says when to prefer it or what to do when a locality is unavailable. The auth-condition note ('uses the official API if DIYANET_EMAIL/DIYANET_PASSWORD are set, otherwise a keyless mirror') is the closest thing to operational guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.