Skip to main content
Glama

Get ayahs

qul_get_verses
Read-only

Retrieve the Arabic text of a single ayah or range within a surah, with optional translations, metadata, and word-by-word data for Quran study or app integration.

Instructions

Get the Arabic text of one ayah or a range inside a surah, optionally with translations and word-by-word data. For a single ayah pass the same key as from and to, e.g. from "2:255".

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": {
      "from": "<from>"
    },
    "name": "qul_get_verses"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast ayah in the same surah, e.g. "2:257". Defaults to from.
fromYesFirst ayah, e.g. "2:255"
scriptsNoArabic script variants to include. Defaults to text_uthmani.
metadataNoExtra per-ayah fields such as juz_number or sajdah_type
text_formatNo"text" strips HTML and footnote markers (default); "html" returns QUL's markup as-istext
word_fieldsNoWord fields to include when include_words is true, e.g. en_transliteration
include_wordsNoInclude word-by-word breakdown
translation_idsNoTranslation resource IDs to attach (max 10), e.g. [20] for Saheeh International. See qul_list_resources.
word_translation_languageNoISO code for word-by-word meanings, e.g. "en", "ur", "id". Implies include_words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already mark it read-only and open-world; the description adds the important constraint that a range is within one surah and that translations and word data are optional. It does not disclose max range limits, error behavior, or response shape beyond content categories, so it adds some but not rich behavioral context.

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?

Two sentences, front-loaded with the core action, and the single-ayah convention follows immediately. No filler or repetition.

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

Completeness3/5

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

The tool has nine parameters and no output schema, so the description must cover core return content; it identifies Arabic text plus optional translations and word data. It omits scripts, metadata, text_format, and translation limits, leaving important richness to the schema.

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?

Schema description coverage is 100%, so the schema already defines all nine parameters, defaults, enums, and examples. The description reinforces the single-ayah convention by saying to pass the same key for from and to, but this is largely aligned with the schema's `to` default and adds little extra parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific action and resource: retrieving Arabic text for one ayah or a range inside a surah, with optional translations and word-by-word data. This distinguishes it from audio and tafsir siblings, though it does not explicitly 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 Guidelines3/5

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

Gives practical usage for a single ayah (pass the same key as from and to) and implies range usage via from/to inside one surah. It does not state when to choose this over qul_get_translations, qul_get_tafsir, or qul_random_ayah, so alternative selection is left implicit.

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