Skip to main content
Glama
2yousefreda

Islamic Content MCP Server

by 2yousefreda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

islamhouse_quran

Fetch full Surah audio recitations, reciter profiles, and recitation metadata from IslamHouse. Use for audio needs, 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_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_recitations', 'get_recitation_details'
suraIdNoSurah ID (1-114)
languageYesLanguage code (e.g. 'ar', 'en')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / description
      Previous value: -"Required. One of: 'list_categories', 'get_category', 'get_author', 'get_author_recitations', 'get_sura_details', 'get_sura_recitations', 'get_recitation_details'"New value: +"Required. One of: 'list_categories', 'get_category', 'get_author', 'get_author_recitations', 'get_sura_recitations', 'get_recitation_details'"
  2. Addedv1.1.2

TDQS

A4.9/5.0
Behavior5/5

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

Despite no annotations, the description discloses key behavioral traits: read-only, idempotent, no authentication, and 404/empty on invalid IDs. This is rich context beyond what any annotation would provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections. It is thorough but not overly verbose; however, the action mapping repeats schema information (e.g., parameter types), which is slightly redundant but not bloated.

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?

Covers all needed aspects: purpose, behavior, usage, and per-action input/output. Even without an output schema, the action mapping provides return types, making it complete for an agent to call 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?

The description goes beyond the input schema by mapping each action to its required parameters and return types, e.g., `list_categories` -> Category[] with id and title. This adds meaning far beyond the schema's parameter descriptions.

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 fetches Quranic audio recitations, reciter profiles, and Sura metadata, and explicitly contrasts with quran_services (textual translations). This is a specific verb-resource pairing that distinguishes it from siblings.

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?

Provides explicit when-to-use ('full audio recitations...') and when-not-to-use ('Do NOT use for fetching written Quran text/translations') and names the alternative (quran_services).

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