Azan-MCP

by bartest5

Overview Schema Source Related Servers Discussions Admin

Python

Remote

set_iqama_offset

Update the Iqama offset (minutes after adhan) for a chosen prayer. Temporary change that resets on server restart.

Instructions

Update the Iqama offset (minutes after adhan) for a prayer. Change is in-memory only and resets on server restart.

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>",
      "offset_minutes": "<offset_minutes>"
    },
    "name": "set_iqama_offset"
  }
}

Input Schema

Name	Required	Description	Default
`prayer`	Yes
`offset_minutes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description discloses the critical non-persistence trait ('in-memory only and resets on server restart'), which goes beyond the schema and is essential for an agent deciding whether to rely on the change. It does not mention auth or error behavior, but for a simple setter this is sufficient.

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?

One tightly written sentence plus a second sentence for the key behavioral caveat; no filler or repetition. Excellent structure.

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 two-parameter setter, the description covers the action, the offset meaning, and the ephemerality. However, the prayer parameter is left completely unspecified (no enum, no example), which an agent needs for correct invocation. This gap prevents a top completeness score.

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 0%, so the description must carry the semantics. It explains that offset_minutes is a duration in minutes after adhan, which is meaningful, but it does not enumerate acceptable prayer string values or their format. This partial compensation justifies an average score.

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 a specific action ('Update') on a specific resource ('Iqama offset') and defines the offset as 'minutes after adhan' for a prayer. This distinguishes it from the read-only sibling tools like get_iqama_time and get_prayer_times.

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

Usage Guidelines4/5

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

The verb 'Update' and the resource scope 'for a prayer' imply the tool is for changing a prayer's iqama offset, but there is no explicit guidance on when to use this versus reading via get_iqama_time, nor any exclusions or prerequisites. The context is reasonably clear but not explicitly differentiated.

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