Skip to main content
Glama
Sign In

HalalTrip

by com.halaltrip
OverviewDiscussionsAdmin

Ramadan timetable

get_ramadan_timetable
Read-onlyIdempotent

Sahur (ends at Fajr) and iftar (Maghrib) times for every day of this or the next Ramadan in a city, with the expected or announced first day and Eid al-Fitr.

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_ramadan_timetable"
  }
}

Input Schema

NameRequiredDescriptionDefault
asrNoAsr juristic method. Default: Hanafi in Pakistan, India, Bangladesh and Afghanistan, else Shafii.
placeNoCity name, optionally with country: "Kuala Lumpur", "London, United Kingdom".
methodNoCalculation method id from list_calculation_methods. Default: the method of the country's Islamic authority (MUIS, JAKIM, Diyanet, ...), else Muslim World League.
latitudeNoLatitude in degrees, instead of place.
longitudeNoLongitude in degrees, instead of place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 non-open-world behavior, so the safety profile is covered. The description adds genuine context beyond that: the timetable spans every day of the selected Ramadan, and the start date may be "expected or announced," which usefully warns that the first day carries uncertainty. It does not state what happens when the current date falls outside Ramadan or how place versus coordinates are resolved.

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?

A single sentence that front-loads the core resource (sahur and iftar times) and then layers scope and range in parentheses without wasted words. The parenthetical glosses on Fajr and Maghrib are doing real disambiguation work, not padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema the description usefully enumerates what is returned (daily sahur/iftar plus first day and Eid al-Fitr). The notable gap is that all five parameters are optional, yet the description never says what happens if neither place nor latitude/longitude is supplied, leaving an agent unsure whether a zero-argument call is valid or defaults to some location.

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%, with enums, defaults and units documented for asr, method, place, latitude and longitude. The description adds nothing about any of these parameters, so the schema carries the full burden; baseline 3 applies.

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?

"Sahur (ends at Fajr) and iftar (Maghrib) times for every day of ... Ramadan" names a specific resource and defines the two data points precisely, including their boundary prayers. It does not explicitly contrast itself with get_prayer_times, so an agent must infer that this is the Ramadan-scoped variant, but the Ramadan framing is distinctive enough to disambiguate in practice.

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 phrase "this or the next Ramadan" implies the temporal scope in which the tool applies, which is useful routing information. However, there is no explicit when-to-use/when-not statement and no named alternative for non-Ramadan date queries, so the agent must infer that get_prayer_times covers the rest of the year.

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

All HalalTrip 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