Azan-MCP

by bartest5

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_prayer_dua

Retrieve authentic du'as for each position in salah, including ruku, sujood, tashahhud, and after salah.

Instructions

Return du'as for a specific position in salah. position: ruku, sujood, tashahhud, after_salah.

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": {
      "position": "<position>"
    },
    "name": "get_prayer_dua"
  }
}

Input Schema

Name	Required	Description	Default
`position`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 12, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavior. It only states what the tool returns, but does not disclose return format, error handling, or any side effects. This is insufficient for a tool with no annotation coverage.

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 two sentences, direct, and includes only essential information. It front-loads the purpose and clarifies the parameter without unnecessary detail.

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 one-parameter tool, the description covers the purpose and parameter options. However, without an output schema, it does not explain the return format, and it does not differentiate from sibling tools, leaving some gaps for full comprehension.

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

Parameters5/5

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

The schema provides no description for the 'position' parameter (0% coverage), but the description supplies the accepted values (ruku, sujood, tashahhud, after_salah). This is critical for correct invocation and fully compensates for the schema gap.

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 identifies the tool's purpose: returning du'as for a specific position in salah, with examples of positions. This is a specific verb+resource combination that distinguishes it from sibling dua/adkar tools like get_dua_by_topic or get_morning_adhkar.

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. The description implies usage for prayer positions but does not explicitly state when not to use it or mention alternatives such as search_dua or list_dua_topics.

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