Skip to main content
Glama

Wasilah

by io.github.mumullickm
OverviewDiscussionsAdmin

get_next_prayer

Read-only

Get the next upcoming prayer and how long until it begins, for a city or coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asrNo
cityNoCity name to resolve, e.g. "Dhaka" or "Madinah". Ignored when latitude and longitude are given.
methodNo
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
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds minimal behavioral context by mentioning the countdown ('how long until it begins'), but does not disclose details like timezone inference, response format, or potential fallbacks. This aligns with the calibration example for get_calls, scoring a 3.

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 a single, front-loaded sentence with zero fluff. Every word contributes to understanding the tool's purpose and input mode. It is an excellent example of concise, efficient writing.

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?

The tool has 7 optional parameters and no output schema, but the description covers the core purpose and the primary input modes (city/coordinates). It does not explain the full response structure or edge cases, but for a conceptually simple tool, the missing details are largely covered by the schema. This earns a 4, slightly short of a 5 due to the lack of explicit return-value description.

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 71%, with descriptions for city, latitude, longitude, timezone, and offset_minutes. The description itself does not add parameter semantics beyond the schema—it merely restates 'city or coordinates.' The enum parameters (asr, method) rely on their enum values. Since coverage is moderately high and the description doesn't compensate further, a baseline 3 is appropriate.

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's function with a specific verb ('Get'), the resource ('the next upcoming prayer'), and an additional output ('how long until it begins'). It also specifies the input scope ('for a city or coordinates'), which distinguishes it from sibling tools like get_prayer_times.

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

Usage Guidelines4/5

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

The description provides a clear context for when to use this tool: when you need the next prayer and countdown. However, it does not explicitly mention alternatives or exclusions, such as using get_prayer_times for a full schedule. The clarity of the context earns a 4, but the lack of explicit differentiation from siblings prevents a 5.

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