Skip to main content
Glama
2yousefreda

Islamic Content MCP Server

by 2yousefreda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bayan_al_islam

Retrieve curated Islamic content tailored to Muslim and non-Muslim audiences, with translations and structured lookups for targeted answers.

Instructions

Access Bayan Al-Islam to fetch specialized Islamic content targeting Muslims and Non-Muslims, including translated articles and structured lookups. Unlike the general IslamHouse library, this provides curated content categorized by the target audience's faith perspective.

Behavior: Read-only. Idempotent. No authentication. Falls back to default language if translation is missing. Usage Guidelines:

  • Use when seeking content specifically tailored for non-Muslims, or curated responses to common questions.

  • Do NOT use for raw Hadith (use hadeethenc_services) or Quran recitations (use islamhouse_quran or quran_services). Action Mapping:

  • list_languages, list_paginated_languages: language, page (int), [name] -> Returns { languages: [{ code, name }] }

  • list_muslim_content, list_non_muslim_content: language -> Returns { paths: [] }

  • get_content, search_name: id (int) or name (string), language -> Returns { id, title, body, matchingResults: [] }

  • get_recent_contents: ids (array of ints), init (bool), lang (overrides language) -> Returns { recentItems: [] }

  • get_lookups, get_available_languages: id (int), language -> Returns { metadata: [] }

  • get_content_translation, get_attachments_translation: id (int), targetLanguage (ISO-639-1), language -> Returns { translatedBody, attachments: [] } Returns: Concrete JSON payload { id, title, body, paths: [], recentItems: [] } containing targeted content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
idsNo
initNo
langNo
nameNo
pageNo
actionYesRequired. One of: 'list_languages', 'list_muslim_content', 'list_non_muslim_content', 'list_paginated_languages', 'get_recent_contents', 'get_lookups', 'search_name'
languageNo
targetLanguageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / description
      Previous value: -"Required. One of: 'list_languages', 'list_muslim_content', 'list_non_muslim_content', 'get_content', 'list_paginated_languages', 'get_recent_contents', 'get_lookups', 'search_name', 'get_available_languages', 'get_content_translation', 'get_attachments_translation'"New value: +"Required. One of: 'list_languages', 'list_muslim_content', 'list_non_muslim_content', 'list_paginated_languages', 'get_recent_contents', 'get_lookups', 'search_name'"
  2. Changed8 schema fields changedv1.1.12
    • removedInput schema / properties / id / description
      Removed value: -"Content or Category ID"
    • removedInput schema / properties / ids / description
      Removed value: -"Array of content IDs"
    • removedInput schema / properties / init / description
      Removed value: -"Initialization flag"
    • removedInput schema / properties / lang / description
      Removed value: -"Override language code"
    • removedInput schema / properties / language / description
      Removed value: -"Language code (ISO-639-1)"
    • removedInput schema / properties / name / description
      Removed value: -"Search name or filter term"
    • removedInput schema / properties / page / description
      Removed value: -"Page number"
    • removedInput schema / properties / targetLanguage / description
      Removed value: -"Target language for translation (ISO-639-1)"
  3. Changed8 schema fields changedv1.1.11
    • addedInput schema / properties / id / description
      Added value: +"Content or Category ID"
    • addedInput schema / properties / ids / description
      Added value: +"Array of content IDs"
    • addedInput schema / properties / init / description
      Added value: +"Initialization flag"
    • addedInput schema / properties / lang / description
      Added value: +"Override language code"
    • addedInput schema / properties / language / description
      Added value: +"Language code (ISO-639-1)"
    • addedInput schema / properties / name / description
      Added value: +"Search name or filter term"
    • addedInput schema / properties / page / description
      Added value: +"Page number"
    • addedInput schema / properties / targetLanguage / description
      Added value: +"Target language for translation (ISO-639-1)"
  4. 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 full responsibility for behavioral disclosure. It explicitly states 'Read-only. Idempotent. No authentication. Falls back to default language if translation is missing.' This covers safety, repeatability, and edge-case behavior. The action mapping further details return shapes, leaving no surprises.

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. It is front-loaded with the core purpose, and every sentence adds value—no fluff. Despite its length, it's efficiently organized for quick scanning, making it appropriate for the tool's complexity.

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 tool's complexity (9 parameters, multiple actions) and absence of an output schema, the description provides complete action-level parameter configurations and expected return objects. It covers all listed actions and their signatures, making it sufficient for an agent to call correctly without additional external documentation.

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?

Schema description coverage is only 11% (only 'action' has a description), so the description must compensate. It does so via a comprehensive 'Action Mapping' that lists each action and its parameters, e.g., 'get_content': `id` (int) or `name` (string), `language` -> Returns { id, title, body }. This clarifies the role of every parameter across all 9 parameters, exceeding schema adequacy.

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 purpose: 'Access Bayan Al-Islam to fetch specialized Islamic content targeting Muslims and Non-Muslims, including translated articles and structured lookups.' It explicitly contrasts with the general IslamHouse library by emphasizing curated, audience-specific content. This distinguishes it from siblings like `islamhouse_library` and `hadeethenc_services`.

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 when seeking content specifically tailored for non-Muslims, or curated responses to common questions.' It also gives clear exclusions: 'Do NOT use for raw Hadith (use `hadeethenc_services`) or Quran recitations (use `islamhouse_quran` or `quran_services`).' This leaves no ambiguity about sibling selection.

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