Muslim Prayer Reminder MCP

Get Full Daily Prayer Timetable

get_today_prayer_times

Read-onlyIdempotent

Retrieve today's Islamic prayer times for any location, including Fajr, Dhuhr, Asr, Maghrib, and Isha in UTC and local time. Selectable calculation method and madhab ensure accurate schedules.

Instructions

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).

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	Date in YYYY-MM-DD format (defaults to today)
`madhab`	No	Optional Asr shadow jurisprudence override (Shafi or Hanafi)
`userId`	No	Unique user or device ID
`latitude`	No	Optional explicit latitude override
`timezone`	No	Optional IANA timezone override
`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
`timesUtc`	Yes
`timezone`	Yes	Resolved IANA timezone
`localDate`	Yes	Local schedule date YYYY-MM-DD
`timesLocal`	Yes
`coordinates`	Yes
`authorityNotice`	No
`selectionReason`	No
`calculationMethod`	Yes	Active calculation authority
`minuteAdjustments`	No
`authorityDescription`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Sep 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only and idempotent behavior. The description adds value by stating output is provided in both UTC and formatted local time, and by imposing a mandatory user disclosure about the calculation method via authorityNotice. No contradiction with annotations.

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 with no filler: the first front-loads the core purpose, and the second delivers a critical mandatory usage rule. 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?

With an output schema present and safety annotations defining behavior, the description fully covers what is retrieved, the display format, and a mandatory disclosure requirement. Nothing necessary for correct invocation is missing.

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?

The input schema has 100% description coverage with all seven parameters documented, so the schema carries the semantic weight. The description only echoes 'calculation authority method' without adding new parameter-specific detail, earning the baseline score.

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 uses a specific verb ('Retrieves') with a specific resource ('today prayer timetable') and enumerates exactly which prayers are included (Fajr through Isha). This clearly distinguishes the tool from siblings like get_next_prayer or get_prayer_status.

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 makes its scope explicit as the full daily timetable, so an agent can infer when to call it versus a single-prayer or status tool. However, it does not explicitly name alternatives or state when not to use it, missing the full 'when-to-use' treatment.

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

Deploy Server