Convert a Gregorian date to a Hijri (Islamic) date.
Convert a Gregorian date to a Hijri (Islamic) date.
| Name | Required | Description | Default |
|---|---|---|---|
| day | Yes | Gregorian day, 1 to 31. | |
| year | Yes | Gregorian year (e.g., 2026). | |
| month | Yes | Gregorian month, 1 to 12. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, fully covering the safety profile. The description adds no behavioral context such as conversion standard (e.g., Umm al-Qura), timezone handling, or precision.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no wasted words, and the core operation is front-loaded immediately. It is appropriately sized for a simple conversion tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, and all required parameters are documented in the schema. The description is nearly complete for a simple conversion, though it could mention calendar-system caveats that affect Hijri results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so all three required parameters (day, month, year) are already documented with ranges and examples. The description adds no additional meaning beyond what the schema provides, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Convert) and resource/direction (Gregorian date to Hijri date), which inherently distinguishes it from the inverse sibling hijri_to_gregorian. An agent can identify the operation without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides no explicit when-to-use, prerequisites, or alternative guidance. The inverse sibling hijri_to_gregorian exists but is not referenced, leaving the agent to infer that this tool is only for forward conversion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.