Skip to main content
Glama
2yousefreda

Islamic Content MCP Server

by 2yousefreda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

hadeethenc_services

Fetch authentic Hadith texts, categories, and translations by language. Retrieve detailed explanations for specific Hadith IDs.

Instructions

Access HadeethEnc to fetch authentic Hadith texts, categories, and translations in multiple languages. This is the only tool dedicated exclusively to Hadith texts and their detailed explanations.

Behavior: Read-only. Idempotent. No authentication. No strict rate limits. Returns empty if ID not found. Usage Guidelines:

  • Use when the user asks for Prophetic sayings, Hadith translations, or scholarly explanations.

  • Do NOT use for official fatwas or general books (use islamhouse_library or risalat_al_haramain). Action Mapping:

  • list_languages, list_categories, list_root_categories: languageCode (ISO-639-1) -> Returns { categories: [{ id, title, hadeeths_count }] }

  • list_hadiths: language, categoryId (int), page (int), perPage (int) -> Returns { data: [{ id, title }] }

  • get_hadith_details: id (int), language (ISO-639-1) -> Returns { id, hadeeth, explanation, translations: [] } Returns: JSON array for lists or a detailed JSON object containing specific Hadith text and translations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoHadith ID
pageNoPage number
actionYesRequired. One of: 'list_languages', 'list_categories', 'list_root_categories', 'list_hadiths', 'get_hadith_details'
perPageNoItems per page
languageNoLanguage code for lists/details (e.g. 'en')
categoryIdNoCategory ID
languageCodeNoLanguage code for categories (e.g. '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, the description carries the full burden and meets it: it discloses read-only, idempotent, no authentication, no strict rate limits, and empty response for missing IDs. It also outlines the JSON return shape for list and detail actions, so the agent knows what to expect.

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 organized into Behavior, Usage Guidelines, Action Mapping, and Returns, with the core purpose front-loaded. Each section earns its place by adding operational or routing value; there is no filler or tautology.

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 7-parameter service with no output schema and no annotations, the description is complete: it explains every action's parameters, return shape, behavior, and usage boundary. An agent has what it needs to select and call the 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 the schema has 100% description coverage, the description goes further by mapping each action to its relevant parameters and return shape (e.g., list_languages uses languageCode and yields { categories: [...] }, get_hadith_details uses id and language and yields translations). This is meaning the schema alone does not provide.

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 ('fetch') and resource ('Hadith texts, categories, and translations'), and immediately distinguishes this service by calling it 'the only tool dedicated exclusively to Hadith texts and their detailed explanations.' This lets an agent separate it from quran_services and other Islamic-content siblings 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?

Explicit Usage Guidelines state use for Prophetic sayings, Hadith translations, and scholarly explanations, and explicitly say not to use for official fatwas or general books, naming islamhouse_library and risalat_al_haramain as the alternatives. This is clear when-to-use vs when-not-to-use guidance.

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