Muslim Prayer Reminder MCP

Check Muslim Prayer Due Status

get_prayer_status

Read-onlyIdempotent

Checks if a Muslim obligatory prayer (Fajr, Dhuhr, Asr, Maghrib, Isha) is currently due for the user location and returns active reminder details. MANDATORY: The LLM must always explicitly disclose to the user which calculation authority method was used and why it was selected (see authorityNotice in response).

Input Schema

TableJSON Schema

Name	Required	Description
`madhab`	No	Optional Asr shadow jurisprudence override (Shafi or Hanafi)
`userId`	No	Unique user or device ID for preference and deduplication tracking
`latitude`	No	Optional explicit latitude override
`timezone`	No	Optional IANA timezone override (e.g. Asia/Riyadh)
`longitude`	No	Optional explicit longitude override
`calculationMethod`	No	Optional calculation authority override (auto-resolved from location by default)

Output Schema

TableJSON Schema

Name	Required	Description
`madhab`	Yes	Active Asr jurisprudence
`prayer`	No	The name of the currently due prayer if applicable
`timezone`	Yes	Resolved IANA timezone
`dedupeKey`	No	Deduplication cache key
`localDate`	Yes	Current local date in YYYY-MM-DD
`nextPrayer`	Yes	The name of the next upcoming prayer
`reminderDue`	Yes	Whether a prayer is currently due for reminder
`expiresAtUtc`	No	UTC expiration time of the active prayer window
`reminderText`	No	Localized reminder message
`startedAtUtc`	No	UTC start time of the active prayer window
`locationSource`	Yes	Source of location resolution
`authorityNotice`	No	Mandatory theological transparency notice
`nextPrayerAtUtc`	Yes	UTC timestamp of the next upcoming prayer
`selectionReason`	No	Reason for authority selection
`calculationMethod`	Yes	Active calculation authority
`minuteAdjustments`	No	Applied minute adjustments
`authorityDescription`	No	Description of the calculation authority

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 6, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the key behavioral disclosure that the LLM must disclose the calculation authority method used and why, which is exactly the kind of non-obvious behavior an agent needs to know. It also clarifies that the result is location-dependent and that the calculation method is auto-resolved unless overridden.

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?

Two sentences: the first states the core function with the relevant prayer names, the second gives a mandatory compliance instruction. No filler, front-loaded with the core purpose. Every sentence earns its place.

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?

The function is a read-only lookup with an output schema available, all parameters are documented, and the only critical non-obvious requirement (disclosing the calculation method) is explicitly stated. There is no missing information an agent would need to call this tool correctly.

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 six parameters are already documented in the schema. The description adds context that calculationMethod and location overrides are optional and auto-resolved, but the description does not add significant new meaning beyond the schema's own descriptions. 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 checks whether a Muslim obligatory prayer (Fajr, Dhuhr, Asr, Maghrib, Isha) is currently due for the user's location and returns active reminder details. The specific verb 'checks', the resource ('prayer due status'), and the listed prayer names distinguish it clearly from siblings like get_next_prayer and get_today_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 names the sibling tools implicitly through the five prayers and 'due status' framing, and the MANDATORY instruction tells the agent a key practice to follow (disclosing the calculation method). It could explicitly say 'use get_next_prayer for upcoming prayers' or 'use get_today_prayer_times for a schedule', but the due-status wording plus sibling names is clear enough context.

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

All Muslim Prayer Reminder MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools have clearly distinct purposes: configuration, preference retrieval, next prayer timing, current-due status, and the full daily timetable. There is slight potential confusion between get_prayer_status and get_next_prayer because both deal with current/upcoming prayer timing, but their descriptions sufficiently separate 'currently due' from 'immediate next.'

Naming Consistency5/5

All tool names follow a consistent get_/configure_ + noun-phrase pattern in snake_case. The naming is predictable and an agent can infer likely behavior from the verb and object.

Tool Count5/5

Five tools is well-scoped for a prayer reminder server. Each tool covers a distinct need without redundancy or bloat.

Completeness4/5

The set covers configuration, preference retrieval, daily schedule, next prayer, and current due status—core reminder workflows are represented. Minor gaps exist such as no ability to retrieve prayer times for arbitrary dates or list calculation authorities, but these are not blocking for the apparent purpose.

Check Muslim Prayer Due Status

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources