Skip to main content
Glama

thirdtrail

by io.github.thirdtrail
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON 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 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.
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. 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"
+]
  2. 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 and non-destructive, so the safety profile is covered. The description adds genuinely useful non-annotation context: elevation correction of the computed times, the paid-plan auth requirement, and which parameters drive which outputs. It doesn't describe return format, but that is a minor omission.

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?

Front-loaded with the returned values, then usage routing, then defaults and prerequisites. Every sentence carries distinct information with no filler.

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 computation with no output schema, the description covers what is produced, how to choose it over siblings, defaults, the required school parameter, and the auth requirement. Nothing an agent needs to invoke 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 the baseline is 3, but the description adds relational meaning the schema doesn't: school sets the fajr and isha rules, asr_method selects the shadow rule with shafi as default, and date defaults to today. This is more than restating the field list.

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?

Names the exact resource (Fajr, sunrise, dhuhr, asr, maghrib, isha) and the scope (one date at a location, elevation-corrected). It explicitly contrasts itself with the sibling get_sun_moon_times, so an agent can route correctly without opening either 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?

States when to use it ('Islamic prayer schedules') and names the alternative for the non-Islamic case (get_sun_moon_times). It also surfaces prerequisites and defaults: school is required, asr_method defaults to shafi, date defaults to today, and an API key on a paid plan is needed.

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

All thirdtrail toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources