Skip to main content
Glama

Islamic prayer times

get_prayer_times
Read-onlyIdempotent

Fajr, sunrise, dhuhr, asr, maghrib and isha for one date at a location, elevation-corrected. Use it for Islamic prayer schedules; for general sunrise, sunset and twilight use get_sun_moon_times. school is required and sets the fajr and isha rules; asr_method picks the shadow rule and defaults to shafi. date defaults to today. Requires an API key on a paid Ephemerides plan.

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": {
      "lat": "<lat>",
      "lon": "<lon>",
      "school": "<school>"
    },
    "name": "get_prayer_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoIANA timezone for output timestamps, e.g. Europe/Dublin. Defaults to UTC.
latYesLatitude in decimal degrees.
lonYesLongitude in decimal degrees.
dateNoDay as YYYY-MM-DD. Defaults to today.
schoolYesCalculation school: mwl (Muslim World League), isna (Islamic Society of North America), egyptian (Egyptian General Authority of Survey), karachi (University of Islamic Sciences, Karachi), uaq (Umm al-Qura, Makkah).
elevationNoMetres. For sun and moon times this is the observer's height above the horizon they look across: on a sea cliff or island peak, their height above sea level; on a plateau or in a valley, close to zero. For irradiance it is height above sea level. Supply it when known: from a height the sun rises measurably earlier than the sea-level answer. Omit only if it is genuinely unknown.
asr_methodNoAsr shadow rule: shafi (default; also Maliki and Hanbali) or hanafi, which gives a later Asr.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / elevation / description
      Previous value: -"Metres above sea level. Supply it when known: at altitude the sun rises measurably earlier than the sea-level answer. Omit only if the elevation is genuinely unknown."New value: +"Metres. For sun and moon times this is the observer's height above the horizon they look across: on a sea cliff or island peak, their height above sea level; on a plateau or in a valley, close to zero. For irradiance it is height above sea level. Supply it when known: from a height the sun rises measurably earlier than the sea-level answer. Omit only if it is genuinely unknown."
  2. Changed7 schema fields changed
    • changedInput schema / properties / asr_method / description
      Previous value: -"Asr shadow rule."New value: +"Asr shadow rule: shafi (default; also Maliki and Hanbali) or hanafi, which gives a later Asr."
    • changedInput schema / properties / asr_method / enum
      Previous value: -[
      -  "standard",
      -  "hanafi"
      -]New value: +[
      +  "hanafi",
      +  "shafi"
      +]
    • changedInput schema / properties / date / description
      Previous value: -"Day as YYYY-MM-DD."New value: +"Day as YYYY-MM-DD. Defaults to today."
    • changedInput schema / properties / school / description
      Previous value: -"Calculation school: mwl, isna, egypt, makkah, karachi."New value: +"Calculation school: mwl (Muslim World League), isna (Islamic Society of North America), egyptian (Egyptian General Authority of Survey), karachi (University of Islamic Sciences, Karachi), uaq (Umm al-Qura, Makkah)."
    • addedInput schema / properties / school / enum
      Added value: +[
      +  "egyptian",
      +  "isna",
      +  "karachi",
      +  "mwl",
      +  "uaq"
      +]
    • changedInput schema / properties / tz / description
      Previous value: -"IANA timezone for output timestamps, e.g. Europe/Dublin."New value: +"IANA timezone for output timestamps, e.g. Europe/Dublin. Defaults to UTC."
    • changedInput schema / required
      Previous value: -[
      -  "lat",
      -  "lon"
      -]New value: +[
      +  "lat",
      +  "lon",
      +  "school"
      +]
  3. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds real context beyond that by naming a paid-plan API key prerequisite and default behaviors for asr_method and date. It even enumerates the returned time fields, which partially substitutes for the missing output schema.

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?

Four sentences, front-loaded with what is returned, then routing guidance, then required-parameter and default rules, then the access prerequisite. No filler or restated schema prose.

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

Completeness5/5

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

For a 7-parameter read-only tool with no output schema, it covers the returned values, the two behavioral parameters, the two defaults, the elevation rationale implicit in the purpose, and the API-key requirement. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description earns extra credit by explaining what school actually controls (fajr and isha rules) and that asr_method picks the shadow rule with shafi as default. It reinforces the elevation correction without restating the schema text verbatim.

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 the specific resource (Fajr, sunrise, dhuhr, asr, maghrib, isha) for a given date and location, plus the elevation correction, and explicitly separates itself from get_sun_moon_times. An agent can identify both the output and the scope without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('Islamic prayer schedules') and an explicit alternative with its condition ('for general sunrise, sunset and twilight use get_sun_moon_times'). It also flags that school is required, removing the main selection risk.

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.