Skip to main content
Glama

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

Search the treasures

search_treasures
Read-onlyIdempotent

Search the curated treasures (kunuz): short verbatim spans picked from the lectures and classified. wassaya = advices; memorable_quotes = memorable sayings of the scholar; hadith_fawaid = benefits drawn from a hadith; tafsir_fawaid = benefits from a verse; sira_ibrah = lessons from the Sira and history; imam_sayings = sayings of earlier scholars he quotes; glad_tidings = glad tidings; diagnostic_observations = diagnoses of the Ummah's problems; qa_pairs = questions and answers; books_recommended = books he recommends. Matches the verbatim text (Arabic).

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_treasures"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
typesNolimit to these types

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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's one real behavioral addition is that matching happens against verbatim Arabic text, which tells the agent what language/form the query must take; it says nothing about ranking, ordering, or result shape, which keeps it at a 3.

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?

Purpose is front-loaded in the first sentence and the rest is a compact glossary with no filler. The glossary partly repeats the schema enum, but each gloss does add meaning, so the length is largely justified.

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 3-parameter search tool with no output schema, the description covers what is searched and the categories but omits return format, ordering, pagination/capping behavior, and query semantics. It is adequate to invoke but not complete enough to predict results.

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 only 33%, so the description must carry weight; it does gloss each type value (wassaya = advices, hadith_fawaid = benefits from a hadith, etc.) and explains what query matches. It says nothing about how `limit` behaves or whether `types` filters alongside or instead of the query text, leaving a real gap.

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+resource ('Search the curated treasures (kunuz)') and clarifies what a treasure is ('short verbatim spans picked from the lectures and classified'). It does not explicitly differentiate itself from siblings like browse_treasures, search_lectures, or get_treasure, so an agent has to infer the boundary.

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: the verb 'Search' plus 'Matches the verbatim text (Arabic)' suggests a full-text lookup, but there is no explicit when-to-use guidance, no mention of when to prefer browse_treasures or search_lectures, and no statement about whether query is exact vs fuzzy.

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