Skip to main content
Glama

Get recitation audio

qul_get_audio
Read-only

Retrieve audio URLs for Quran recitations by surah or ayah using a recitation ID; list available recitation IDs first when needed.

Instructions

Get audio URLs for a recitation. For a surah_recitation pass chapter; for an ayah_recitation pass chapter and optionally ayah. Find recitation IDs with qul_list_resources.

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": {
      "kind": "<kind>",
      "recitation_id": "<recitation_id>",
      "chapter": "<chapter>"
    },
    "name": "qul_get_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
ayahNoOnly for kind=ayah: one ayah number in the surah
kindYes"surah" for surah_recitations IDs, "ayah" for ayah_recitations IDs
chapterYesSurah number, 1-114
recitation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description still adds the important behavioral fact that the result is URLs rather than audio bytes, and that an ID must be obtained first. It does not mention what an ayah-kind call without the ayah parameter returns, which is the one remaining behavioral ambiguity.

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?

Three short sentences, front-loaded with the purpose, then the per-kind parameter rule, then the prerequisite. No filler and nothing repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly identifies the return value as audio URLs, and it covers the ID acquisition path. It could be sharper about the result shape when ayah is omitted for an ayah-type recitation, which is the only meaningful remaining gap for a four-parameter tool.

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

Parameters4/5

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

Schema coverage is 75% and the schema already explains kind, chapter and ayah. The description adds real value by explaining the kind-conditional parameter combination and by compensating for the undocumented recitation_id with a pointer to qul_list_resources.

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?

States a specific verb and resource ('Get audio URLs for a recitation') and immediately branches by the two kinds the tool supports, so an agent can tell it apart from timing, tafsir, translation and verse siblings without opening a schema. The only friction is the naming of 'surah_recitation'/'ayah_recitation' versus the schema enum values 'surah'/'ayah', which the schema resolves.

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?

Gives clear conditional instructions on which parameters to pass for each kind, plus the prerequisite that recitation IDs come from qul_list_resources. It does not state when another sibling (e.g. qul_get_ayah_timings) would be the better choice, so it stops short of explicit exclusions.

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