Wesalna Islamic MCP

Get prayer times

get_prayer_times

Read-onlyIdempotent

Calculate the five daily prayer times plus sunrise, imsak, midnight and the last third of the night for a latitude and longitude, or by city and/or country name (226 countries, 2,500+ cities, English or Arabic), on a given date. Output includes a required attribution link to show with the data.

Input Schema

Name	Required	Description
`city`	No	City name or slug in English or Arabic, e.g. amman or عمان. Supplies coordinates, timezone and method.
`date`	No	Gregorian date as YYYY-MM-DD. Defaults to today (UTC).
`method`	No	Calculation method. Defaults to MuslimWorldLeague.
`country`	No	ISO code or country name, e.g. JO. Alone it returns the capital.
`madhhab`	No	Asr calculation school. Defaults to shafi.
`latitude`	No	Latitude in decimal degrees. Not needed when city is given.
`timezone`	No	IANA timezone used to render local clock times, e.g. Asia/Amman.
`longitude`	No	Longitude in decimal degrees. Not needed when city is given.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / city / description

Previous value: -"Supported city slug such as makkah or london, from list_prayer_cities. Supplies coordinates, timezone and suggested method."New value: +"City name or slug in English or Arabic, e.g. amman or عمان. Supplies coordinates, timezone and method."

addedInput schema / properties / country

Added value: +{
+  "description": "ISO code or country name, e.g. JO. Alone it returns the capital.",
+  "maxLength": 60,
+  "minLength": 2,
+  "type": "string"
+}

First observedSep 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent safety, so the description adds real value beyond them: the required attribution link in the output, dataset breadth (226 countries, 2,500+ cities, English/Arabic), and the extra time values beyond the five prayers. Missing only notes on default-resolution behavior when no location is supplied.

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 front-loaded sentence covering scope, inputs, and the attribution constraint with no filler. It is dense and slightly run-on, but every clause carries information.

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 no output schema, the description correctly notes the attribution requirement and enumerates returned time values. The only real gap is the zero-required-parameter case, where the resolution rule for a location-less call is unstated.

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 the either/or semantics between coordinate and city/country modes that the schema only hints at per-parameter. It does not, however, explain what happens when neither coordinate nor place is given.

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 verb (calculate) and resource (five daily prayer times plus sunrise, imsak, midnight, last third), plus both input modes (lat/long or city/country). This clearly separates it from siblings like list_prayer_cities and get_qibla.

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 by the input modes described, but there is no explicit guidance on when to prefer this over list_prayer_cities (to discover valid city names) or get_qibla. No exclusions or prerequisites given.

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

All Wesalna Islamic MCP tools Inspect

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

Need Help?