HalalTrip

Prayer times

get_prayer_times

Read-onlyIdempotent

Daily prayer times (Fajr, sunrise, Dhuhr, Asr, Maghrib, Isha) for a city or coordinates, for a date or up to 31 days, with the Hijri date.

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": "get_prayer_times"
  }
}

Input Schema

Name	Required	Description
`asr`	No	Asr juristic method. Default: Hanafi in Pakistan, India, Bangladesh and Afghanistan, else Shafii.
`date`	No	First day, YYYY-MM-DD. Default: today at the place.
`days`	No	Number of days, 1 to 31. Default 1.
`place`	No	City name, optionally with country: "Kuala Lumpur", "London, United Kingdom".
`method`	No	Calculation method id from list_calculation_methods. Default: the method of the country's Islamic authority (MUIS, JAKIM, Diyanet, ...), else Muslim World League.
`latitude`	No	Latitude in degrees, instead of place.
`longitude`	No	Longitude in degrees, instead of place.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds value by disclosing the return contents (six named times plus the Hijri date), which matters because there is no output schema. It does not discuss defaults resolution or behavior when no locator is supplied.

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?

One sentence, front-loaded with the resource name, and every clause maps to something an agent needs: output fields, locator options, date range and the Hijri date. Nothing is wasted.

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 seven-parameter, all-optional read tool with full schema coverage and rich annotations, the description covers scope and returned data adequately. The only gap is how defaults resolve when neither place nor coordinates are provided, which the schema only partially covers.

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 description coverage is 100%, so the baseline is 3; every parameter including method, asr, date and days already documents its defaults and ranges. The description only restates the city/coordinates and date/31-day grouping, adding no syntax or precedence guidance beyond the schema.

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?

The description names a specific verb+resource (returns daily prayer times) and enumerates exactly which times (Fajr, sunrise, Dhuhr, Asr, Maghrib, Isha), plus the accepted locators (city or coordinates) and range (a date or up to 31 days). It is clear what the tool does, but it does not contrast itself with near siblings like get_ramadan_timetable or get_islamic_calendar.

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?

Usage is only implied: the mention of 'a city or coordinates' and 'up to 31 days' hints at the calling context, but there is no explicit when-to-use statement, no exclusion of alternatives such as the Ramadan timetable, and no guidance on which locator to prefer.

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

All HalalTrip tools Inspect

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

Need Help?