Skip to main content
Glama

List surahs

qul_list_chapters
Read-only

Lists all 114 Quran surahs with Arabic and transliterated names, translated names by locale, verse counts, and revelation places for chapter lookup and metadata.

Instructions

List all 114 surahs with Arabic and transliterated names, translated name, verse count and revelation place.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "qul_list_chapters"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoISO code for translated names, e.g. "en", "ar", "ur". Defaults to English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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's real contribution is disclosing the shape of each returned entry (name variants, verse count, revelation place), which matters because there is no output schema. It says nothing about ordering, completeness guarantees, or response size for a fixed 114-item list.

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?

One sentence, front-loaded with the action and scope, then the return fields. Every clause carries information; nothing is redundant or padded.

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 parameterless, read-only list call the description is nearly sufficient: it names the count, the fields returned, and the language dimension. The only gap is that the enumerated fields act as a substitute for a missing output schema without stating item ordering or that all entries are always returned.

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 100%, and the schema already explains that locale is an ISO code controlling translated names with an English default. The description's mention of "translated name" corroborates that but adds no syntax, fallback behavior, or validation detail beyond the schema. 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?

"List all 114 surahs" is a specific verb plus resource with an explicit scope, and the enumerated return fields (Arabic/transliterated/translated name, verse count, revelation place) make the output concrete. It implicitly separates itself from the single-chapter sibling qul_get_chapter by promising the complete set, but it never names 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?

Usage is only implied: an agent can infer this is the browse/index call to make before calling qul_get_chapter or qul_get_verses. There is no explicit when-to-use statement, no exclusion, and no mention of when a filtered or single-chapter lookup would be preferable.

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