Skip to main content
Glama

Get surah info

qul_get_chapter
Read-only

Retrieve metadata for a specific Quran surah, including names, verse count, revelation place and order, and mushaf page range.

Instructions

Get details for one surah: names, verse count, revelation place and order, mushaf page range.

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": {
      "chapter": "<chapter>"
    },
    "name": "qul_get_chapter"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoISO code for translated names, e.g. "en", "ar", "ur". Defaults to English.
chapterYesSurah number, 1-114

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 and reach profile is covered externally. The description contributes the concrete payload contents an agent would actually want. It does not mention error behavior for out-of-range surah numbers or whether results are cached, which limits it to adequate.

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?

A single sentence with zero filler, front-loading the action and resource before the field list. Every clause carries information an agent can act on.

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?

With no output schema and only two parameters, the description sensibly serves as the return-value contract by naming the fields returned. What is missing is only edge behavior, such as what happens for an invalid chapter or an unsupported locale, which is minor for a simple read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the chapter range 1-114 and the locale ISO-code behavior both documented in the schema. The description reinforces this by advertising "names" as a returned field, implying locale-dependent translated names. No semantic gap remains for either parameter.

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 pairs a specific verb ("Get") with a specific resource ("details for one surah") and enumerates exactly which fields come back: names, verse count, revelation place and order, mushaf page range. That makes it clearly distinguishable in practice from the list-style sibling qul_list_chapters, though it never names that sibling explicitly.

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 implied rather than stated: "for one surah" signals a single-record lookup as opposed to a listing, and the enumerated fields suggest it is the metadata source for chapter-level facts. There is no explicit when-to-use/when-not guidance and no pointer to qul_list_chapters or qul_get_verses for related needs.

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