Skip to main content
Glama
Sign In
madeenan

madeenan

by itsmunzir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

lookup_quran_reference

Retrieve a Quran verse, chapter, or bounded passage by reference for source-based citation and study. Provide a reference like 2:255, a chapter number, or start and end ayah values.

Instructions

Read one Quran verse, chapter, or bounded passage by reference.

Use ``2:255`` for one verse, ``2`` for a chapter, or ``2`` with start and
end ayah values for a passage. The returned text is a source lookup only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reference": "<reference>"
    },
    "name": "lookup_quran_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_ayahNo
referenceYes
start_ayahNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations, so the description carries the full burden; it does set the key boundary that output is raw source text and not interpretation ("a source lookup only"), which is useful. It says nothing about invalid or out-of-range references, ayah numbering conventions, or failure behavior for a tool that takes free-form references.

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?

Three short sentences, front-loaded with the action, followed by the format examples and the source-only caveat. Nothing is padded or restated from the title.

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

Completeness4/5

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

For a simple read-only lookup with an output schema already covering return shape, the description supplies the reference grammar an agent needs to call it correctly. Gaps are minor: error behavior and the exact ayah indexing convention are left implicit.

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 0%, but the description compensates well: it defines the reference string formats and explains that start_ayah/end_ayah convert a chapter lookup into a bounded passage. It does not address precedence when reference already contains an ayah range while start_ayah is also set, nor whether a lone start_ayah is honored.

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 Quran verse, chapter, or bounded passage") and enumerates the three scope modes it supports. Because the sibling tools are keyed to different resources (hadith, dua), the resource itself distinguishes it without needing to name an alternative.

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

Usage Guidelines4/5

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

Gives concrete invocation patterns per mode — ``2:255`` for a verse, ``2`` for a chapter, ``2`` plus start/end for a passage — which is real when-to-use-this-way guidance. It stops short of saying when to use this instead of search_islamic_sources or find_quote_source, so there is no exclusion 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