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
} |
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 | Configures prayer calculation parameters, location behavior (fixed or auto_travel), madhab, reminder mode, and notification language in persistent storage. |
| get_prayer_preferencesA | Returns the currently active calculation settings and preferences for a user. Read-only operation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The read operations target distinct temporal scopes: get_prayer_status checks a currently due prayer, get_next_prayer returns the upcoming prayer, and get_today_prayer_times provides the full daily schedule. There is slight potential for confusion between status and next prayer in edge cases, but the descriptions make the differences mostly clear.
All tool names follow a consistent snake_case pattern with clear verb prefixes: get_ for read operations and configure_ for the write operation. The resource nouns (prayer_status, today_prayer_times, next_prayer, prayer_preferences) are descriptive and follow a predictable convention.
Five tools is well-scoped for a focused prayer reminder server: three read tools cover prayer time retrieval and status, while two tools handle preference configuration. Each tool earns its place without redundancy or unnecessary expansion.
The tool set covers the core prayer reminder workflow: current status, daily timetable, next prayer, and preference management. Minor gaps include lack of support for arbitrary date queries and no explicit tool for listing supported calculation methods, but these are workable around the existing surfaces.