Skip to main content
Glama

Get tafsir

qul_get_tafsir
Read-only

Retrieve tafsir (Quranic commentary) for a specific ayah or range, or fetch multiple tafsirs for one verse, with numbered parts for complete long commentary.

Instructions

Get tafsir (commentary) for an ayah. Pass resource_id for one tafsir (optionally over a range), or omit it to get several tafsirs for one ayah. Tafsir entries often cover a group of ayahs; see the verses field. Text is always complete: long tafsir comes in numbered parts, and the response's next.call says how to get the next one.

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_tafsir"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast ayah of the range (only with resource_id). Defaults to from.
fromYesAyah key as "chapter:verse", e.g. "2:255"
partNoLong tafsir is split into parts, never cut. Pass the part number from the previous response's next.call.
limitNoWhen not using resource_id: how many different tafsirs to include
languageNoWhen not using resource_id: limit to one language, e.g. "en"
resource_idNoOne tafsir ID, e.g. 169 (Ibn Kathir, English)
text_formatNo"text" strips HTML and footnote markers (default); "html" returns QUL's markup as-istext
resource_idsNoWhen not using resource_id: limit to these IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavioral guarantees — that text is never truncated, that long tafsir is split into numbered parts, and that the response's next.call carries the continuation instruction. It also warns that a tafsir entry may cover several ayahs and points to the verses field. It does not describe overall response shape (no output schema exists), leaving a small gap.

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 sentences, front-loaded with the core action, then the mode split, then the completeness/pagination caveat. Each sentence carries distinct operational information with no filler or repetition.

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 an 8-parameter read tool with no output schema, the description covers the high-risk failure modes: wrong mode selection, truncated text, and how to continue via next.call. What is thinner is the return payload beyond 'verses' and 'next.call' — the agent gets no sense of the fields holding the tafsir text itself, which matters given no output 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 documents every parameter including the resource_id vs. resource_ids/limit/language split and the part mechanism. The description restates the mutually exclusive modes and ties 'part' to next.call, both of which are already in the schema text. It adds coherence but little new parameter meaning, so baseline 3 applies.

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 a specific verb and resource ('Get tafsir (commentary) for an ayah') and immediately clarifies the two operating modes: single tafsir by resource_id vs. multiple tafsirs for one ayah. It does not name a sibling (e.g. qul_get_translations) to contrast against, so it stops short of full differentiation, but the purpose itself is unambiguous.

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 explicit selection logic: 'Pass resource_id for one tafsir (optionally over a range), or omit it to get several tafsirs for one ayah', which is a clear when-to-do-which. It also tells the agent to consult the verses field when entries span a group of ayahs. It lacks an explicit when-not-to-use or a named alternative tool, which keeps it from a 5.

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