Skip to main content
Glama
2yousefreda

Islamic Content MCP Server

by 2yousefreda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

islamhouse_quran

Retrieve full-Surah Quran audio recitations, reciter profiles, and recitation metadata from IslamHouse. Use for audio recitations or reciter info; not for text translations.

Instructions

Access IslamHouse to fetch Quranic audio recitations, reciter (author) profiles, and Sura recitation metadata. Unlike quran_services, this specializes in high-quality, full-Sura audio recitations and reciter catalogs rather than textual translations.

Behavior: Read-only. Idempotent. No authentication. Returns 404/empty on invalid IDs, with safe fallbacks on missing audio. Usage Guidelines:

  • Use for full audio recitations of the Quran or reciter information (e.g., Al-Sudais).

  • Do NOT use for fetching written Quran text/translations (use quran_services instead). Action Mapping:

  • list_categories: language (ISO-639-1) -> Category[] { id: number, title: string }

  • get_category, get_author: language (ISO-639-1), id (int) -> { id, title, description, count }

  • get_author_recitations: id (author ID, int), language (ISO-639-1) -> { data: [{ recitationId, title }] }

  • get_sura_details, get_sura_recitations: suraId (int 1-114), language (ISO-639-1) -> { suraId, name, recitations: [] }

  • get_recitation_details: id (recitation ID, int), language (ISO-639-1) -> { id, reciterId, audioUrl, duration }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoCategory, Author, or Recitation ID
actionYesRequired. One of: 'list_categories', 'get_category', 'get_author', 'get_author_recitations', 'get_sura_details', 'get_sura_recitations', 'get_recitation_details'
suraIdNoSurah ID (1-114)
languageYesLanguage code (e.g. 'ar', 'en')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and delivers: it states 'Read-only. Idempotent. No authentication. Returns 404/empty on invalid IDs, with safe fallbacks on missing audio.' This goes beyond basic safety to disclose error behavior and fallback semantics, far exceeding the minimum expected.

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 structured with clear headers (Behavior, Usage Guidelines, Action Mapping) and front-loaded purpose. Every section contributes distinct information—no filler. While longer than average, the length is justified by the tool's multi-action nature, and the formatting makes it easy to scan.

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

Completeness5/5

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

Given the absence of an output schema and the tool's breadth (7 actions), the description comprehensively covers required contexts: purpose, alternatives, behavior, parameter usage per action, and output shapes. It includes error handling and fallback behavior, leaving no obvious gaps an agent would need to call this tool correctly.

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?

Although schema coverage is 100%, the description adds significant value by mapping each action to the exact parameters it expects (e.g., list_categories→language, get_author_recitations→id+language) and by specifying output shapes like { data: [{ recitationId, title }] }. This clarifies the polymorphic 'id' parameter across actions, which the schema alone does not fully explain.

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 opens with a specific verb and resource: 'fetch Quranic audio recitations, reciter (author) profiles, and Sura recitation metadata.' It also differentiates itself from the sibling quran_services by explicitly stating it focuses on audio and reciter catalogs rather than textual translations, giving unambiguous purpose clarity.

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

Usage Guidelines5/5

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

The description contains explicit Usage Guidelines: use for full audio recitations or reciter info, and 'Do NOT use for fetching written Quran text/translations (use quran_services instead).' It also provides a detailed Action Mapping that ties each action to its expected parameters and output, effectively guiding tool selection for every intended use case.

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

Deploy Server

Other Tools