Skip to main content
Glama
Sign In

Prayer Times

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Hijri Calendar

hijri_calendar
Read-onlyIdempotent

Monthly Islamic prayer-times calendar for a city: per-day Gregorian and Hijri (Islamic calendar) dates with salah times (Fajr, Dhuhr, Maghrib, Isha).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "Cairo",
      "year": 2026,
      "month": 6,
      "country": "Egypt"
    },
    "name": "hijri_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name, e.g. "London".
yearYesGregorian year, e.g. 2026.
monthYesGregorian month, 1-12.
methodNoPrayer-time calculation method. Default 2 = ISNA; 3 = MWL; 4 = Umm al-Qura; and others.
countryYesCountry name or code, e.g. "UK".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "city": "Cairo",
+    "country": "Egypt",
+    "month": 6,
+    "year": 2026
+  },
+  {
+    "city": "Dubai",
+    "country": "UAE",
+    "method": 4,
+    "month": 12,
+    "year": 2026
+  }
+]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint=false, covering safety and idempotency. The description adds that it returns per-day dates and salah times, but does not disclose rate limits, precision of times, or any other behavioral details beyond what annotations provide.

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?

Single, front-loaded sentence that immediately conveys the tool's purpose. Every word earns its place; no redundancy or filler.

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?

For a monthly calendar retrieval tool with no output schema, the description adequately explains what is returned (per-day dates, both calendars, five salah times). It could mention output format or scope but is sufficiently complete for typical use.

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 coverage is 100% with each parameter described (city, year, month, method, country). The description does not add meaning beyond the schema; it only describes the output. Baseline 3 is appropriate.

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 clearly states it provides a monthly Islamic prayer-times calendar for a city, including per-day Gregorian and Hijri dates with five salah times. This distinguishes it from sibling tools like prayer_times (likely daily only), qibla (direction), and convert_to_hijri (date conversion only).

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

Usage Guidelines3/5

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

The description implies usage for obtaining a monthly prayer calendar, but it does not explicitly tell when to use this tool versus siblings like prayer_times or convert_to_hijri. No when-not-to or alternative selection guidance is provided.

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

All Prayer Times toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources