Muslim Prayer Reminder MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_prayer_statusA | 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). |
| get_today_prayer_timesA | Retrieves today prayer timetable (Fajr, Sunrise, Dhuhr, Asr, Maghrib, Isha) in UTC and formatted local time. 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). |
| get_next_prayerA | Returns the immediate next prayer name, scheduled time, authority calculation method, and remaining countdown in minutes. 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). |
| configure_prayer_preferencesA | Updates persistent prayer preferences, overwriting supplied settings while preserving omitted settings. Setting fixedCity replaces stored fixedCoordinates and stores the canonical city timezone; contradictory timezones are rejected; setting fixedCoordinates replaces stored fixedCity. Can disable reminders. Fixed mode requires a supported fixedCity or fixedCoordinates with timezone; new coordinates require timezone in the same request. clearFixedLocation removes saved location and timezone and defaults to auto_travel. Combined fixed-location calculation settings are validated for the current and next local day before saving. Invalid combinations preserve the previous preferences. Auto-travel chronology is checked when a query supplies its location. Previous values are not retained for undo. |
| get_prayer_preferencesB | Returns the currently active calculation settings and preferences for a user. Read-only operation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| check_prayer_times_with_disclosure | Get today's prayer times for an explicitly supplied city or location, including regional calculation provenance and potential mosque differences. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| prayer-calculation-guide | Reference for location selection, Asr convention, twilight calculation, high-latitude limitations, and local mosque differences. |
TDQS
Scored across 5 tools
Each tool targets a distinct question: current due status, today's timetable, next prayer countdown, read preferences, and update preferences. The overlapping domain (prayer times) is cleanly partitioned by purpose, so an agent can select the right tool without ambiguity.
All names follow a consistent snake_case verb_noun pattern: get_* for read operations and configure_* for the write operation. The convention is predictable and readable throughout.
Five tools is well-scoped for a prayer reminder server: three focused query tools and two preference-management tools. Each tool earns its place, and there is no obvious redundancy.
The surface covers the core lifecycle: current status, daily timetable, next prayer, and preference read/update. Minor gaps exist, such as querying prayer times for an arbitrary date or month, but agents can work around them for typical reminder workflows.