Skip to main content
Glama

Prayer Times

by io.github.pipeworx-io

Prayer Times

prayer_times
Read-onlyIdempotent

Islamic prayer times (salah times: Fajr, Sunrise, Dhuhr, Asr, Maghrib, Isha, plus Imsak and Midnight) for a location today. Provide either city+country or latitude+longitude. Returns timings, Gregorian and Hijri (Islamic calendar) dates, timezone, and the calculation method used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity name, e.g. "London". Requires country.
methodNoPrayer-time calculation method. Default 2 = ISNA (Islamic Society of North America); 3 = MWL (Muslim World League); 4 = Umm al-Qura (Makkah); and others.
countryNoCountry name or code, e.g. "UK". Requires city.
latitudeNoLatitude in decimal degrees. Use with longitude as an alternative to city+country.
longitudeNoLongitude in decimal degrees. Use with latitude.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "city": "London",
+    "country": "UK"
+  },
+  {
+    "latitude": 51.5074,
+    "longitude": -0.1278,
+    "method": 3
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds context: that it returns timings, Gregorian and Hijri dates, timezone, and method used, which helps agent understand output.

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; first lists the times, second explains inputs and outputs. Every word is useful, no redundancy.

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?

Given no output schema, the description mentions what is returned (timings, dates, timezone, method). Parameter count 5 with full schema coverage and examples suffice for agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (all parameters have descriptions). The description further explains the relationship between city/country and lat/lon, and provides example method values, adding meaning beyond schema.

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 returns Islamic prayer times (listing all times) for a location today, which is a specific verb-resource pair. It distinguishes from sibling tools like qibla (direction) and convert_to_hijri (date conversion).

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 explains two input methods (city+country or lat/lon) and mentions it's for today. It does not explicitly say when not to use it or list alternatives, but the purpose is clear and sibling tools are distinct.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, though there is some overlap between `ai_visibility_check` and `scan_competitor_ai_presence`, and between `bet_research` and `polymarket_edges`. Overall, an agent can distinguish them.

Naming Consistency3/5

Tool names follow snake_case but vary in prefix usage (e.g., `pipeworx_*`, `polymarket_*`, no prefix) and verb presence (e.g., `discover_tools` vs. `generate_llms_txt`). The pattern is readable but inconsistent.

Tool Count2/5

With 24 tools, the server is overloaded for the 'Prayer Times' name. Many tools are unrelated to prayer, suggesting poor scoping relative to the server's implied purpose.

Completeness2/5

For prayer times, the server includes core tools but lacks features like multi-day forecasts or advanced settings. However, the inclusion of many unrelated tools makes the set incoherent and incomplete for any single domain.

Resources