Skip to main content
Glama

Muslim Prayer Reminder MCP

Configure User Prayer Preferences

configure_prayer_preferences
DestructiveIdempotent

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localeNoLanguage for reminder text: en or ar
madhabNoJurisprudential Asr shadow calculation: Shafi or Hanafi
userIdYesNonblank user identifier; at most 256 UTF-8 bytes and 256 characters. Whitespace in nonblank identifiers is preserved.
enabledNoWhether prayer reminders are enabled
timezoneNoIANA timezone identifier (e.g. Asia/Riyadh, Europe/London)
fixedCityNoSupported cities: makkah, madinah, riyadh, cairo, gaza, jerusalem, alquds, ramallah, hebron, nablus, rafah, khanyunis, dubai, abudhabi, kuwait, doha, amman, istanbul, london, paris, newyork, toronto, jakarta, singapore, karachi, kualalumpur, tehran, sydney, tromso. Aliases: gazacity, nyc, kuwaitcity. Case, spaces and punctuation are ignored.
locationModeNoLocation strategy: fixed uses saved location; auto_travel requires the caller to supply current city or coordinates/timezone on each query and never uses IP geolocation.
reminderModeNoReminder display policy: prayer_window, exact_window, persistent
fixedCoordinatesNoFixed geographical coordinates
highLatitudeRuleNoHigh latitude twilight adjustment rule
calculationMethodNoIslamic prayer calculation authority
minuteAdjustmentsNoCustom per-prayer minute offsets (-60 to +60). For fixed locations, combined settings must preserve timetable chronology for the current and next local day before saving; auto-travel offsets are validated when a query supplies its location.
clearFixedLocationNoRemove stored fixedCity, fixedCoordinates and timezone. Switches to auto_travel unless locationMode is supplied. Cannot combine with a new fixed location/timezone.
exactWindowMinutesNoDuration in minutes for exact_window mode. Omitted updates preserve the saved value; if unset, the service default is 20 minutes unless the operator overrides it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesWhether configuration succeeded
preferencesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / minuteAdjustments / description
      Previous value: -"Custom per-prayer minute offsets (-60 to +60)"New value: +"Custom per-prayer minute offsets (-60 to +60). For fixed locations, combined settings must preserve timetable chronology for the current and next local day before saving; auto-travel offsets are validated when a query supplies its location."
  2. Changed3 schema fields changed
    • changedInput schema / properties / exactWindowMinutes / description
      Previous value: -"Duration in minutes for exact_window mode"New value: +"Duration in minutes for exact_window mode. Omitted updates preserve the saved value; if unset, the service default is 20 minutes unless the operator overrides it."
    • changedInput schema / properties / locationMode / description
      Previous value: -"Location strategy: auto_travel or fixed"New value: +"Location strategy: fixed uses saved location; auto_travel requires the caller to supply current city or coordinates/timezone on each query and never uses IP geolocation."
    • addedInput schema / properties / userId / pattern
      Added value: +"\\S"
  3. Changed4 schema fields changed
    • addedInput schema / properties / clearFixedLocation
      Added value: +{
      +  "description": "Remove stored fixedCity, fixedCoordinates and timezone. Switches to auto_travel unless locationMode is supplied. Cannot combine with a new fixed location/timezone.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / fixedCity / description
      Previous value: -"Predefined city name for fixed location (e.g. Riyadh, London)"New value: +"Supported cities: makkah, madinah, riyadh, cairo, gaza, jerusalem, alquds, ramallah, hebron, nablus, rafah, khanyunis, dubai, abudhabi, kuwait, doha, amman, istanbul, london, paris, newyork, toronto, jakarta, singapore, karachi, kualalumpur, tehran, sydney, tromso. Aliases: gazacity, nyc, kuwaitcity. Case, spaces and punctuation are ignored."
    • changedInput schema / properties / userId / description
      Previous value: -"Unique user identifier"New value: +"Nonblank user identifier; at most 256 UTF-8 bytes and 256 characters. Whitespace in nonblank identifiers is preserved."
    • addedInput schema / properties / userId / maxLength
      Added value: +256
  4. Changed3 schema fields changed
    • addedOutput schema / properties / preferences / properties / fixedCityConfigured
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / preferences / properties / fixedCoordinatesConfigured
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / preferences / required
      Added value: +[
      +  "fixedCoordinatesConfigured",
      +  "fixedCityConfigured"
      +]
  5. Changed2 schema fields changed
    • removedOutput schema / properties / preferences / properties / fixedCoordinates
      Removed value: -{
      -  "additionalProperties": false,
      -  "properties": {
      -    "latitude": {
      -      "type": "number"
      -    },
      -    "longitude": {
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "latitude",
      -    "longitude"
      -  ],
      -  "type": "object"
      -}
    • removedOutput schema / properties / preferences / properties / userId
      Removed value: -{
      -  "type": "string"
      -}
  6. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / fixedCoordinates / additionalProperties
      Removed value: -false
    • removedInput schema / properties / minuteAdjustments / additionalProperties
      Removed value: -false
  7. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.