MCP-Dubai

quran_search

Read-onlyIdempotent

Search the Quran for a phrase. Filter by surah, select an edition, and paginate through matching verses.

Instructions

Search the Quran for a phrase.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum matches to return, from 1 to 100. Defaults to 25.
`query`	Yes	Phrase to search for.
`surah`	No	Surah number or "all".	all
`offset`	No	Zero-based match offset for pagination.
`edition`	No	Edition slug or language code (e.g., "en" or "ar").	en

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.4.1Oct 22, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 25,
+  "description": "Maximum matches to return, from 1 to 100. Defaults to 25.",
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Zero-based match offset for pagination.",
+  "type": "integer"
+}

First observedv0.4.0Jul 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no note on how results are ranked, whether matching is exact-phrase or fuzzy, or how language/edition affects matches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler. It is efficient, though its brevity is close to under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, and the input schema is fully documented, which keeps the tool usable. Still, for a 5-parameter search with a surah filter and edition/language switch, the description gives no hint that results can be scoped or paginated, leaving the agent to discover capability entirely from the schema.

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 description coverage is 100% with defaults and ranges documented for every parameter, so the schema carries parameter meaning entirely. The description mentions 'phrase' which loosely maps to the required query, but adds no semantics for surah scoping, edition, limit or offset — baseline 3 is appropriate.

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?

States a specific verb (search) and resource (the Quran) plus the search unit ('a phrase'), which is enough to tell it apart from the reference-style siblings quran_surah, quran_ayah and quran_juz. It stops short of explicitly contrasting itself with those siblings, so it is clear but not maximally differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus quran_surah/quran_ayah (e.g., 'use when you don't know the verse reference'), no mention of language/edition selection behavior, and no exclusions. The agent must infer the routing decision from the sibling names alone.

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

Deploy Server