Skip to main content
Glama
2yousefreda

Islamic Content MCP Server

by 2yousefreda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

quran_services

Fetch Quranic text translations, list available translations, and retrieve single-ayah audio clips using QuranEnc data.

Instructions

Access QuranEnc to fetch Quran textual translations, translations lists, and ayah-level audio. Unlike islamhouse_quran, this tool specializes strictly in text-based translations of meanings and single-ayah audio, rather than full recitations or reciter data.

Behavior: Read-only. Idempotent. No authentication required. No strict rate limits. Usage Guidelines:

  • Use this tool when you need the textual translation of an Ayah or Sura in a specific language, or a short audio clip of one Ayah.

  • Do NOT use this tool for full Sura recitations or fetching reciter profiles (use islamhouse_quran instead). Action Mapping & Parameters:

  • list_translations: Requires language (optional localization). Returns a JSON array of available translations.

  • get_sura_translation: Requires translationKey and suraNumber. Returns a JSON object with the translation of the full Sura.

  • get_aya_translation: Requires translationKey, suraNumber, and ayaNumber. Returns a JSON object with the specific Ayah's text.

  • get_aya_audio: Requires translationKey, suraNumber, and ayaNumber. Returns a JSON object with an audio URL for the Ayah. Returns: A JSON array or object containing the requested QuranEnc data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesRequired. One of: 'list_translations', 'get_sura_translation', 'get_aya_translation', 'get_aya_audio'
languageNoLanguage code (e.g. 'en')
ayaNumberNoAyah number
suraNumberNoSurah number (1-114)
localizationNoLocalization language (e.g. 'en')
translationKeyNoTranslation identifier (e.g. 'en_sahih')

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 meets it: 'Read-only. Idempotent. No authentication required. No strict rate limits.' It also describes what each action returns, giving the agent a clear behavioral contract.

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 well-structured with clear sections: purpose, behavior, usage guidelines, action mapping, and returns. Every sentence adds practical value, and the most important differentiator is front-loaded.

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?

For a tool with 6 parameters, no annotations, and no output schema, the description is remarkably complete: it covers safety, idempotency, authentication, rate limits, action-specific parameter requirements, return types, and when to use the sibling tool instead.

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 the input schema has 100% field-level coverage, the description adds substantial meaning by mapping each action to its required and optional parameters. This tells the agent which parameters to provide for list_translations, get_sura_translation, get_aya_translation, and get_aya_audio—information not present in the schema alone.

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: 'Access QuranEnc to fetch Quran textual translations, translations lists, and ayah-level audio.' It explicitly contrasts with islamhouse_quran, so an agent can distinguish this tool from its sibling without inspecting schemas.

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 guidance: 'Use this tool when you need the textual translation of an Ayah or Sura in a specific language, or a short audio clip of one Ayah.' It also gives a clear exclusion: 'Do NOT use this tool for full Sura recitations or fetching reciter profiles (use islamhouse_quran instead).'

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