Skip to main content
Glama
Sign In

Quran Gallery MCP

by com.qurangallery
OverviewDiscussionsAdmin
This connector has been deprecated

this is duplicate of the https://glama.ai/mcp/connectors/com.qurangallery/mcp

Read a library page

fetch
Read-onlyIdempotent

Read one library page whole by the id search returned: main text, then its footnotes under their own label (the editor's words, never the author's), with book, author, printed volume/page, edition data and the link to the page in the Quran Gallery Maktabah reader. Use shamela_read instead to read one body part at a time (unit "page"), a run of pages (unit "range") or a whole chapter (unit "section"), and shamela_cite (mode "printed_page") to turn a printed volume and page into ids. Not a search. Long pages are cut at 4 body parts of about 4,000 characters (2 without an API key): metadata.complete false, ending with the shamela_read call that continues it. A malformed id, or a page the library does not hold, returns a tool error.

Input Schema

NameRequiredDescriptionDefault
idYesPage id "{bookId}:{pageId}", e.g. "1681:10" — Shamela internal ids from a `search` result, not printed page numbers. Malformed or unknown ids return a tool error.

Output Schema

NameRequiredDescriptionDefault
idNo"{bookId}:{pageId}", normalised.
urlNoThe same page in the Quran Gallery Maktabah reader.
textNoMain text, then the footnotes under their own label (the editor's words). When metadata.complete is false it ends with the shamela_read(unit='page') call that continues it.
titleNo"{book} — {author} ({volume}/{page})".
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / url / description
      Previous value: -"The same page on shamela.ws."New value: +"The same page in the Quran Gallery Maktabah reader."
  2. Changed12 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"A document id from `search`, e.g. \"117359:1796\"."New value: +"Page id \"{bookId}:{pageId}\", e.g. \"1681:10\" — Shamela internal ids from a `search` result, not printed page numbers. Malformed or unknown ids return a tool error."
    • addedOutput schema / properties / id / description
      Added value: +"\"{bookId}:{pageId}\", normalised."
    • addedOutput schema / properties / metadata / properties / authorDied / description
      Added value: +"Year of death in AH, or null."
    • addedOutput schema / properties / metadata / properties / edition / description
      Added value: +"Omitted when the library records none."
    • addedOutput schema / properties / metadata / properties / editor / description
      Added value: +"Omitted when the library records none."
    • addedOutput schema / properties / metadata / properties / printedPage / description
      Added value: +"Volume and page as the printing paginates it, or null."
    • addedOutput schema / properties / metadata / properties / publisher / description
      Added value: +"Omitted when the library records none."
    • removedOutput schema / properties / metadata / required
      Removed value: -[
-  "bookId",
-  "pageId",
-  "book",
-  "author",
-  "authorDied",
-  "printedPage",
-  "hasFootnotes",
-  "complete"
-]
    • changedOutput schema / properties / text / description
      Previous value: -"Main text, then the footnotes under their own label."New value: +"Main text, then the footnotes under their own label (the editor's words). When metadata.complete is false it ends with the shamela_read(unit='page') call that continues it."
    • addedOutput schema / properties / title / description
      Added value: +"\"{book} — {author} ({volume}/{page})\"."
    • addedOutput schema / properties / url / description
      Added value: +"The same page on shamela.ws."
    • removedOutput schema / required
      Removed value: -[
-  "id",
-  "title",
-  "text",
-  "url",
-  "metadata"
-]
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing truncation behavior (4 body parts, ~4,000 chars, 2 without an API key), the metadata.complete=false signal, and the continuation call shamela_read. It also states error behavior for malformed or unheld ids. Slight gap: "the editor's words, never the author's" for footnotes is evocative but not fully operationalized.

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?

Information-dense and front-loaded with the core action, and every clause carries distinct information. However, the middle is a long run-on sentence with nested em-dash asides, which costs readability for an agent parsing quickly.

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?

Output schema exists, so return values need not be spelled out, yet the description still flags the truncation/continuation contract that the schema cannot express. Combined with the error semantics and sibling routing, nothing needed to invoke this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description earns above that by tying the id to a `search` result in prose and pointing to shamela_cite mode "printed_page" as the conversion path from printed references. It reinforces the id-derivation constraint rather than restating the format 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?

States a specific verb and resource ("Read one library page whole by the id") and enumerates exactly what comes back: main text, footnotes under their own label, book/author/volume/page/edition metadata, and reader link. It distinguishes itself from siblings both positively (shamela_read, shamela_cite) and negatively ("Not a search").

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 routing: use shamela_read for unit "page", "range", or "section"; use shamela_cite mode "printed_page" to convert printed references into ids; this tool is not for searching. The agent knows precisely when this tool is and is not the right choice.

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

All Quran Gallery MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources