Azan-MCP

by bartest5

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_counter_recommendation

Retrieve the recommended repetition count and virtues for a specific dhikr by entering its ID.

Instructions

Return the recommended repetition count and virtues for a specific dhikr by its ID.

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": {
      "dhikr_id": "<dhikr_id>"
    },
    "name": "get_counter_recommendation"
  }
}

Input Schema

Name	Required	Description	Default
`dhikr_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool returns a repetition count and virtues, which is useful, but it does not mention error behaviors (e.g., invalid/nonexistent ID), data format, or whether the operation is read-only. The description gives some transparency but lacks depth.

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, front-loaded sentence that states the action and key output without waste. It is appropriately concise for a simple tool.

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?

Given the tool's simplicity (one parameter, no output schema), the description is mostly sufficient but lacks detail about the output structure (e.g., what exactly 'virtues' includes) and edge-case behavior. It does not explain the meaning of 'recommended count' or how it relates to other adhkar tools, leaving some gaps.

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?

The schema description coverage is 0%, so the description must compensate for explaining the parameter. It only repeats 'by its ID' without elaborating on what a dhikr_id looks like, where to find it, or any constraints. This adds minimal value beyond the parameter name itself.

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's function: returning the recommended repetition count and virtues for a specific dhikr by ID. It uses a specific verb ('Return') and names the resource (dhikr recommendation), distinguishing it from sibling list tools like 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 Guidelines3/5

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

The phrase 'by its ID' implies this tool is for retrieving a single dhikr's recommendation rather than listing all adhkar, but there is no explicit guidance on when to prefer this over sibling tools (e.g., get_morning_adhkar). Usage context is implied, not explicit.

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