Skip to main content
Glama

Mishkat (مِشكاة) Arabic Islamic lectures

Where a verse is discussed

find_verse_discussions
Read-onlyIdempotent

Where in the lectures a Quran verse is recited or explained, with the verse's mushaf text (Hafs) and the tafsir benefits drawn from it.

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": {
      "surah": "<surah>",
      "ayah": "<ayah>"
    },
    "name": "find_verse_discussions"
  }
}

Input Schema

NameRequiredDescriptionDefault
ayahYes
limitNo
surahYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description usefully discloses return content (mushaf text in Hafs, tafsir benefits), but says nothing about result ordering, how the limit behaves, or what an empty result means — notable given there is no output schema.

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 no filler, and the return contents are attached compactly. It is tight but under-specified relative to the schema burden it carries.

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?

For a simple read-only lookup the description covers purpose and partial return content, but with no output schema and zero parameter documentation, an agent cannot tell from the text that it must pass numeric surah/ayah or how large a page to request.

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

Parameters2/5

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

Schema description coverage is 0% for 3 parameters, so the description must compensate and does not: surah, ayah, and limit are never mentioned, nor are the surah 1-114 / ayah 1-286 bounds or the default and maximum for limit. The verse concept is implied but no parameter meaning is added.

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 resource and relation: locating where a Quran verse is recited or explained in lectures, plus the mushaf text and tafsir benefits returned. This distinguishes it from retrieval siblings like get_lecture or search_lectures, though it never names the verse-lookup inputs 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 only implied by the phrasing 'where in the lectures' — an agent can infer this is a verse-indexed lookup rather than a keyword search. No when-to-use / when-not-to-use guidance and no mention of alternatives such as search_lectures.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources