Azan-MCP

Overview Schema Source Related Servers Discussions Admin

get_iqama_time

Get Iqama time for any named prayer (fajr, dhuhr, asr, maghrib, isha) with optional date. Returns the prayer time adjusted by the configured offset.

Instructions

Return the Iqama time (adhan + configured offset) for a given prayer. prayer: fajr, dhuhr, asr, maghrib, isha.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prayer": "<prayer>"
    },
    "name": "get_iqama_time"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No
`prayer`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description itself must disclose behavior. It does explain that the result is based on a configured offset applied to adhan, which is helpful. However, it fails to mention the optional date parameter, timezone considerations, or error behavior, leaving gaps in transparency.

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?

The description is a single, focused sentence that front-loads the purpose and immediately lists valid prayer values. Every word earns its place with no redundancy or fluff.

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?

For a simple read-only tool, the core behavior is covered, but the optional date parameter is not explained and the return format is unspecified. Given no output schema, the description should provide more context to be fully complete.

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

Parameters2/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. It does provide valid values for the 'prayer' parameter, but the 'date' parameter is completely ignored. Thus, only half of the parameters receive semantic explanation.

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 the tool returns the Iqama time for a given prayer, using a specific formula ('adhan + configured offset'). It lists valid prayer values, distinguishing it from siblings like get_prayer_times or set_iqama_offset.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as get_prayer_times or get_daily_azan_schedule. The description only states the basic function, implying usage without explaining context or exclusions.

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