Skip to main content
Glama
Sign In

Prayer Times

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Convert To Hijri

convert_to_hijri
Read-onlyIdempotent

Convert a Gregorian date to the Hijri (Islamic) calendar date. Useful for Islamic calendar date conversion.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "07-06-2026"
    },
    "name": "convert_to_hijri"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesGregorian date in DD-MM-YYYY format, e.g. "07-06-2026".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "date": "07-06-2026"
+  }
+]
  2. First observed

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, so the tool is safe. The description adds no behavioral details beyond the conversion action, such as handling of invalid dates or output format. It relies on annotations for safety but provides no extra context.

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?

Two sentences with no unnecessary words. The purpose is stated first, making it easy for an agent to quickly understand the tool's function.

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?

Given the simple conversion task, good annotations, and clear parameter schema, the description is generally adequate. However, it lacks information about the return value (e.g., format of Hijri date), which is a gap since there is no output schema.

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 100% with a clear description of the date parameter format (DD-MM-YYYY). The tool description does not add extra semantic information beyond what the schema already provides, so baseline 3 is appropriate.

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?

The description clearly states it converts a Gregorian date to the Hijri calendar date, with a specific verb and resource. This purpose is distinct and well-defined.

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 description says 'Useful for Islamic calendar date conversion,' which implies usage context but does not specify when to use this tool versus alternatives like hijri_calendar. No explicit guidance on prerequisites or when not to use it.

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

All Prayer Times 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