Skip to main content
Glama

Get translations

qul_get_translations
Read-only

Fetch Quran translations for ayah ranges or compare several translations of one ayah by resource ID, language, and text format.

Instructions

Get translations from one translation for a range of ayahs, or from several translations for one ayah. Pass resource_id with from/to for a passage, or omit resource_id to compare translations of a single ayah.

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

Input Schema

NameRequiredDescriptionDefault
toNoLast ayah of the range (only with resource_id). Defaults to from.
fromYesAyah key as "chapter:verse", e.g. "2:255"
limitNoMaximum translations returned
languageNoWhen comparing one ayah: limit to one language, e.g. "en"
resource_idNoOne translation ID, e.g. 20 (Saheeh International)
text_formatNo"text" strips HTML and footnote markers (default); "html" returns QUL's markup as-istext
resource_idsNoWhen comparing one ayah: limit to these translation IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds real behavioral information by explaining that omitting resource_id silently switches the tool into a fundamentally different comparison mode over resource_ids, which is genuinely useful. It does not mention result ordering, the effect of the limit default of 10, or whether comparison mode caps the number of translations compared.

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, zero filler, and the multi-mode structure is front-loaded so an agent can branch on it immediately. Every clause carries operational meaning.

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 7-parameter read tool with no output schema, the description covers the essential branching logic and the schema supplies full per-parameter documentation. Remaining gaps — result shape, ordering, and comparison-mode limits — are modest given the complete schema descriptions and the read-only annotation.

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 the baseline would be 3, but the description goes beyond the schema by explaining the conditional relationship between resource_id, resource_ids, and the from/to range — a coupling that the flat schema does not express. It still says nothing about how language or text_format interact with the two modes, which are left entirely to the schema.

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?

The description names a specific verb and resource ('get translations') and immediately enumerates two distinct modes: one translation over a passage, or several translations of a single ayah. It falls short of a 5 because it never distinguishes itself from adjacent siblings like qul_get_tafsir or qul_get_verses, which an agent could plausibly confuse with translation retrieval.

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?

Clear conditional routing is given: pass resource_id with from/to for a passage, omit resource_id to compare a single ayah across translations. This is explicit when-to-use guidance for the tool's own two branches. It stops short of naming alternatives (e.g. when to prefer tafsir or verses instead), so no exclusion guidance is present.

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