Skip to main content
Glama

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

Search the lectures

search_lectures
Read-onlyIdempotent

Find the passages of the lectures where the scholar speaks about a subject or answers a question. Returns verbatim passages (his words as transcribed), grouped by lecture, each with a timestamped link. Arabic queries work best. Use this first for any question about what the scholar says.

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": {
      "query": "<query>"
    },
    "name": "search_lectures"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesthe subject or question, preferably in Arabic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description goes beyond that by disclosing the output contract the agent cannot see elsewhere (verbatim quotes, grouped by lecture, timestamped links) and by flagging a language preference that affects result quality.

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?

Three short sentences, front-loaded with what the tool does and what it returns, followed by query advice and routing priority. Every sentence adds distinct information with no repetition of the title or schema.

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 two-parameter search tool with no output schema, the description supplies the return shape and ordering, which is the main gap that would otherwise exist. Only the limit parameter's effect on results is left unaddressed.

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 50%: the query parameter is documented in the schema, and the description reinforces it with 'Arabic queries work best.' The limit parameter is never mentioned in the description, so the agent has no guidance on pagination or result-count tradeoffs beyond the schema's default and maximum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Find the passages of the lectures where the scholar speaks about a subject or answers a question.' It also states the return shape (verbatim transcribed passages, grouped by lecture, timestamped links) and asserts precedence with 'Use this first for any question about what the scholar says,' which separates it from the topical and verse-oriented siblings.

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

Usage Guidelines4/5

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

'Use this first for any question about what the scholar says' gives clear entry-point guidance relative to the other search tools, and 'Arabic queries work best' is actionable query advice. It stops short of naming an explicit alternative or a when-not condition, so it falls short of the top score.

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