Skip to main content
Glama
Sign In

HalalTrip

by com.halaltrip
OverviewDiscussionsAdmin

Islamic calendar

get_islamic_calendar
Read-onlyIdempotent

The Hijri date for a day, the next key Islamic dates (Ramadan, Eid al-Fitr, Day of Arafah, Eid al-Adha, Islamic New Year, ...) and month starts announced by Islamic authorities.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD. Default: today.
countryNoTwo-letter ISO country code (SG, MY, GB, ...) to use that country's announced dates. Default: Umm al-Qura (Saudi Arabia).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful provenance by saying dates are announced by Islamic authorities and lists included date types, but it does not clarify how far ahead 'next' key dates extend or how authority variation affects results beyond what the schema already states.

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?

It is a single compact sentence with the main outputs front-loaded and no filler. However, it is a fragment/list with an ellipsis and no explicit verb, which slightly weakens structure.

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 two-parameter read-only lookup with no output schema, the description names the main return categories: Hijri date, upcoming key dates, and month starts. It leaves some ambiguity about output shape and the 'next' horizon, but no critical invocation information is absent.

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%, and the schema already documents the date format/default and the country ISO code/default Umm al-Qura behavior. The description adds no parameter-level meaning beyond that, so the baseline of 3 is appropriate.

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 states that the tool returns the Hijri date for a day, upcoming key Islamic dates, and month starts announced by Islamic authorities. That is a clear resource and scope, but it is a noun phrase without an explicit verb and does not directly differentiate itself from siblings such as get_ramadan_timetable.

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 content implies this is for Hijri date and key Islamic date lookups, but the description gives no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer that prayer times, qibla direction, and Ramadan timetables are separate tools.

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