Skip to main content
Glama
2yousefreda

Islamic Content MCP Server

by 2yousefreda

islamhouse_quran_sura_details

Retrieve detailed information about any Quran surah from IslamHouse, including verses and context, in your chosen language.

Instructions

Get IslamHouse details of a specific surah.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
suraIdYesSura ID (1-114)
languageYesLanguage code
Behavior1/5

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

No annotations provided, and the description gives no behavioral traits. It doesn't disclose what 'details' includes, whether it is read-only, or any limitations. The description fails to compensate for missing annotations.

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?

A single, front-loaded sentence with no wasted words. Concisely conveys the tool's purpose without extraneous information.

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

Completeness2/5

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

Given no output schema and no behavioral transparency, the description lacks completeness. It does not explain what the 'details' consist of or provide any context about the response format, making it insufficient for an agent to fully understand the tool's output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already describes both parameters (suraId: 'Sura ID (1-114)', language: 'Language code'). The description adds no extra meaning beyond that. Baseline 3 is appropriate for 100% schema coverage.

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 retrieves details for a specific surah from IslamHouse. It distinguishes from siblings like islamhouse_quran_sura_recitations which focus on recitations, and other item details tools.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. There is no mention of when not to use it or what other tools might be more appropriate for different needs.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/2yousefreda/islamic-content-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server