Skip to main content
Glama

List QUL resources

qul_list_resources
Read-only

Lists available Quran translations, tafsirs, languages, and recitations with the IDs other tools require, and filters results by language or query.

Instructions

List available translations, tafsirs, languages, or recitations, with the IDs other tools take. Use language and query to narrow the list; translations alone number about 200.

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": {
      "type": "<type>"
    },
    "name": "qul_list_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYessurah_recitations are one audio file per surah (most have ayah timings); ayah_recitations are one file per ayah
limitNo
queryNoCase-insensitive match on name, author, slug or language
languageNoISO code to filter translations/tafsirs, e.g. "en", "ur". Ignored for recitations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 safety is covered. The description usefully adds that results carry IDs consumed by other tools and that the translation set is large, but it says nothing about result ordering, pagination/truncation at the default limit of 50, or the shape of returned records.

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 tight clauses, purpose front-loaded before the filtering advice, and the size hint placed where it motivates using limit/query. No filler or restated 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 read-only list tool with annotations and no output schema, the definition covers what it returns at a high level (IDs for other tools) and why filtering matters. It could still say what fields each entry exposes (e.g. name, author, language) since no output schema exists.

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 coverage is 75% and the enum plus the recitation-type distinction are already documented in the schema itself. The description's only additions are that language/query narrow the list and the approximate corpus size — marginal meaning beyond structured fields, so baseline 3.

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 (list) plus the exact resource families (translations, tafsirs, languages, recitations) and adds 'with the IDs other tools take', which separates this discovery tool from the sibling get_* retrieval tools. An agent can pick it out of the catalog without opening the schema.

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?

'Use language and query to narrow the list' gives concrete filtering guidance, and the ~200-translations note signals that unfiltered listing is expensive. It stops short of an explicit when-not or of naming a sibling to prefer, so it remains context rather than a routing rule.

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