Skip to main content
Glama

Iqamah prayer times

Prayer times for a place

get_prayer_times
Read-only

Azaan (start) times for Fajr, sunrise, Dhuhr, Asr, Maghrib and Isha at a point, for one or more days. Uses the country's usual method unless one is given, and the official authority's timetable where we hold it (Malaysia, Indonesia, Singapore, Kazakhstan, Morocco). These are not a mosque's congregation (iqamah) times; for those use find_mosques_near and get_mosque_times.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_prayer_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
asrNoAsr: standard (Shafi'i, Maliki, Hanbali) or hanafi. Default: the country's or method's.
dateNoFirst day, YYYY-MM-DD. Default: today at the location.
daysNo
methodNoCalculation method. Default: the country's usual one.
latitudeYes
longitudeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real behavioral context: automatic method selection by country and the existence of authoritative timetables for five specific countries. It stops short of stating anything about return format, timezone handling, or limits.

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?

Three tight sentences: what it returns first, then the method/timetable behavior, then the disambiguation. No filler and no repetition of schema content.

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 read-only, single-purpose tool with no output schema, the description covers purpose, defaults, and alternatives well. The notable remaining gap is that it never says what a returned time looks like or which timezone it is expressed in — material for a time-of-day tool.

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 50%, with latitude, longitude, and days undocumented in the schema; the description compensates only partially, conveying that a point is required and that days supports multiple days, but never explaining coordinate format or the 7-day cap. Method and asr defaults are covered by the schema descriptions themselves, so the description adds little there.

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?

States a specific resource (Azaan/start times for the six named prayers) plus scope (at a point, one or more days), so an agent knows exactly what comes back. It also distinguishes itself from get_mosque_times by explicitly contrasting start times with iqamah/congregation times.

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

Usage Guidelines5/5

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

Gives explicit defaulting rules ('uses the country's usual method unless one is given'), names the countries where an official authority timetable is used instead, and explicitly excludes the congregation-times case, routing to find_mosques_near and get_mosque_times.

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