Retrieve a complete chapter from the Quran by specifying its surah number (1–114, defaults to 1). Use it to fetch full chapter text for reading or research.
Get a full surah (chapter) from the Quran.
| Name | Required | Description | Default |
|---|---|---|---|
| number | No | Surah number (1-114, default 1) |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'Get' implies a read, but it says nothing about what a surah response contains (Arabic text, translation, verse count, language options), whether results are large, or whether the surah is returned whole or paginated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single tight sentence with no waste. It is appropriately sized, though very short definitions on a bare tool leave room for more useful front-loaded context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema and no annotations, so the description is the only place return content and safety profile could be conveyed. It omits what a full surah actually returns (text, translation, verse structure) and how it differs from quran_verse, which is a real gap for an agent composing a call.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%: the 'number' parameter already documents the 1-114 range and default of 1. The description adds no syntax or semantics beyond that, which meets the baseline when the schema does the work.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Get) and resource (a full surah/chapter), and the parenthetical clarifies the domain term. It does not name the sibling quran_verse or explain the verse-vs-surah distinction, but an agent can infer the difference from 'full surah'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance at all. There is a sibling (quran_verse) that an agent could easily confuse with this one, and the description never says which to pick or under what conditions, leaving the routing decision to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.