Skip to main content
Glama

Prayer times and sun times

Islamic prayer times

prayer_times
Read-onlyIdempotent

Prayer times (imsak, fajr, sunrise, dhuhr, asr, maghrib, isha, midnight) for a town, city or coordinates, in local time, for one day or a timetable of up to 31 days. Covers 34,000 towns worldwide (names in English or Arabic). Calculation method defaults to the usual one for the country (Umm al-Qura in Saudi Arabia, Egyptian in Egypt, Karachi in Pakistan, ISNA in North America, MWL elsewhere) and is always stated; asr standard or hanafi.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prayer_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
asrNoAsr juristic method; default standard (hanafi in PK, IN, BD, AF).
dateNoYYYY-MM-DD; default today in the place's timezone.
daysNoNumber of days from date (timetable). Default 1.
placeNoTown or city name, optionally with country: "Riyadh", "Birmingham, UK", "القاهرة". Or use latitude/longitude.
methodNoCalculation method; default by country.
countryNoOptional ISO 3166-1 alpha-2 code or country name to pick among same-named towns.
latitudeNo
timezoneNoIANA timezone for coordinates, e.g. "Europe/London". Default: from the nearest town.
longitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds real value: coverage of 34,000 towns, English/Arabic name support, and the rule that the calculation method always defaults by country and is reported back. However it says nothing about response shape (ordering, field formats, missing-town behavior), which matters for a 9-parameter lookup.

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 dense sentences, with the resource and field list front-loaded. The country-to-method mapping is long but earns its place by telling the agent what default to expect; nothing is 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 9-parameter, zero-required lookup with no output schema, the description covers locator options, date range limits, timezone, method defaults and asr school. Gaps are minor: coordinates parameters are undocumented and the return format is only implied by the field list.

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

Parameters4/5

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

Schema coverage is 78%, so the baseline is 3; the description goes beyond it by explaining that method is country-defaulted (Umm al-Qura, Egyptian, Karachi, ISNA, MWL) while the method param only says "default by country", and it clarifies English/Arabic place names. Latitude/longitude remain undocumented in both schema and description.

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 resource (prayer times) with the exact returned fields enumerated (imsak, fajr, sunrise, dhuhr, asr, maghrib, isha, midnight), plus the accepted locators (town/city/coordinates) and time span. It never names the sibling tools (prayer_methods, sun_times), so the boundary with them is left to inference.

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?

Gives clear usage context: supply a place name or coordinates, one day by default or a timetable up to 31 days, local time. It does not state when to prefer prayer_methods or sun_times instead, so the routing guidance stops short of exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources