Skip to main content
Glama
MCP Urdu Toolkit

MCP Urdu Toolkit

hijri_date

Converts an ISO date (YYYY-MM-DD) into an approximate Hijri date in English and Urdu, with an optional day offset to align with local moon-sighting calendars.

Instructions

Approximate Hijri (Islamic) date for an ISO date (YYYY-MM-DD, default today), in English and Urdu. Use offset_days (e.g. -1) to match the local moon-sighting calendar.

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

Input Schema

NameRequiredDescriptionDefault
dateNo
offset_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden, and it does flag the key trait: the result is *approximate*, not an authoritative sighting-based date. It also discloses the default (today) and the intended purpose of offset_days. It does not describe what the response looks like or how invalid dates are handled, but as a side-effect-free computation the risk profile is low.

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, both load-bearing — the first establishes the conversion and output languages, the second gives the one non-obvious correction knob. Front-loaded with the operation and free of filler.

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 simple two-parameter, zero-required, side-effect-free conversion with no output schema, the description covers input, default, output languages, and the approximation caveat. The remaining gap is the return shape — it says results are given 'in English and Urdu' but not whether that is two fields or one combined string, which an agent would need for parsing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: it gives the accepted date format (YYYY-MM-DD), the default (today), and explains offset_days with a concrete example (-1) and its purpose (aligning to local moon-sighting). Neither parameter is left unexplained, though the sign/direction semantics of the offset are only implied by the example.

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 transformation: an ISO date (YYYY-MM-DD) in, an approximate Hijri date out, rendered in English and Urdu. That is a concrete verb-plus-resource statement an agent can act on. It does not explicitly differentiate from the sibling utilities, but those (convert_digits, format_pkr, normalize_pk_phone, urdu_text_stats) are not confusable with a calendar conversion, so the omission costs little.

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 implies the use case (convert a given or current date to Hijri) and gives one piece of operational guidance — use offset_days to align with a local moon-sighting calendar. It never states when this tool should be preferred over alternatives or when it should not be used, so the guidance is implied rather than explicit.

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