Skip to main content
Glama

Wasilah

by io.github.mumullickm
OverviewDiscussionsAdmin

get_prayer_times

Read-only

Get the five daily prayer times plus sunrise for a city or coordinates, computed with the same engine as the Wasilah app. On Fridays, Dhuhr is marked as Jumu’ah.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asrNoAsr juristic method. "auto" follows the calculation method’s regional default.
cityNoCity name to resolve, e.g. "Dhaka" or "Madinah". Ignored when latitude and longitude are given.
dateNoDate as YYYY-MM-DD. Defaults to today in the location’s timezone.
methodNoCalculation method. Defaults to "karachi" (the app default).
latitudeNoLatitude in degrees, north positive.
timezoneNoIANA timezone, e.g. "Asia/Dhaka". Used with explicit latitude/longitude. If omitted, the zone is inferred from the nearest known city and reported in the answer.
longitudeNoLongitude in degrees, east positive.
offset_minutesNoOptional per-prayer adjustment in whole minutes, matching the offset settings in the Wasilah app, e.g. {"maghrib": 3}. Applies to the five obligatory prayers only; Sunrise is never offset. These are the user's own adjustments, not a calculation method.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / offset_minutes
      Added value: +{
+  "additionalProperties": false,
+  "description": "Optional per-prayer adjustment in whole minutes, matching the offset settings in the Wasilah app, e.g. {\"maghrib\": 3}. Applies to the five obligatory prayers only; Sunrise is never offset. These are the user's own adjustments, not a calculation method.",
+  "properties": {
+    "asr": {
+      "type": "integer"
+    },
+    "dhuhr": {
+      "type": "integer"
+    },
+    "fajr": {
+      "type": "integer"
+    },
+    "isha": {
+      "type": "integer"
+    },
+    "maghrib": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone, e.g. \"Asia/Dhaka\". Used with explicit latitude/longitude. Defaults to UTC if omitted."New value: +"IANA timezone, e.g. \"Asia/Dhaka\". Used with explicit latitude/longitude. If omitted, the zone is inferred from the nearest known city and reported in the answer."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral context: computation uses the same engine as the Wasilah app, and Friday Dhuhr is marked as Jumu'ah. This goes beyond the annotations without repeating them.

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?

The description is two sentences, front-loaded with the core purpose and followed by a key edge-case behavior. No wasted words; every sentence adds value.

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?

With 8 parameters, a nested object, and no output schema, the description is brief but sufficient for a read-only retrieval tool. It mentions the main input modes (city/coordinates), the engine provenance, and the Friday behavior. It does not detail the return format, but the phrase 'Get the five daily prayer times plus sunrise' implies the response contents.

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%, so all parameters are already documented in the schema. The description adds minimal parameter-related meaning beyond stating 'for a city or coordinates,' which relates to city/latitude/longitude. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

The description clearly states the tool retrieves the five daily prayer times plus sunrise for a city or coordinates. The verb 'Get' is specific, the resource is well-defined, and the scope distinguishes it from sibling tools like get_next_prayer or get_hijri_date.

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?

The description implies usage for retrieving daily prayer times but does not explicitly state when to use this tool versus alternatives like get_next_prayer. There is no mention of 'use this when you need all five times' or 'use get_next_prayer for the next prayer only.' Clear context is present, but no exclusion or alternative guidance.

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

All Wasilah 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