Muslim Prayer Reminder MCP

Retrieve Stored Prayer Preferences

get_prayer_preferences

Read-onlyIdempotent

Retrieves a user's active prayer time calculation settings and preferences so you can verify how their prayer times are configured. Read-only lookup by user ID.

Instructions

Returns the currently active calculation settings and preferences for a user. Read-only operation.

Input Schema

Name	Required	Description	Default
`userId`	Yes	Nonblank user identifier; at most 256 UTF-8 bytes and 256 characters. Whitespace in nonblank identifiers is preserved.

Output Schema

Name	Required	Description	Default
`locale`	No
`madhab`	No
`enabled`	No
`message`	No
`timezone`	No
`fixedCity`	No
`locationMode`	No
`reminderMode`	No
`updatedAtUtc`	No
`highLatitudeRule`	No
`calculationMethod`	No
`minuteAdjustments`	No
`exactWindowMinutes`	No
`fixedCityConfigured`	Yes
`fixedCoordinatesConfigured`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.1.3Oct 22, 2026

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
```
addedInput schema / properties / userId / pattern
```
Added value: +"\\S"
```
addedOutput schema / properties / fixedCityConfigured
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / fixedCoordinates

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "latitude": {
-      "type": "number"
-    },
-    "longitude": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "latitude",
-    "longitude"
-  ],
-  "type": "object"
-}

addedOutput schema / properties / fixedCoordinatesConfigured
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / userId

Removed value: -{
-  "type": "string"
-}

addedOutput schema / required

Added value: +[
+  "fixedCoordinatesConfigured",
+  "fixedCityConfigured"
+]

First observedv1.0.1Sep 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so 'Read-only operation' merely restates structured data. The only added behavioral value is 'currently active', which hints that inactive/stored-but-unused preferences are excluded from the result.

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?

Two short sentences, front-loaded with the resource description. The second sentence is redundant with readOnlyHint and could be cut, a minor waste rather than a structural flaw.

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?

An output schema exists, so return values need no explanation, and annotations fully cover the safety profile. For a one-parameter read tool the description is nearly sufficient; only the missing routing guidance versus sibling tools leaves a small gap.

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% and the single userId parameter is fully documented with pattern and length constraints, so the schema does the heavy lifting. The description adds nothing about the parameter, which is the expected baseline for this coverage level.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Returns) and resource (calculation settings and preferences) with the scoping qualifier 'currently active', which separates it from the write-oriented sibling configure_prayer_preferences. It never names that sibling, so differentiation is inferable rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives. An agent must infer from the tool name alone that this is the read counterpart to configure_prayer_preferences and not, say, a status check like get_prayer_status.

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

Deploy Server