Skip to main content
Glama

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

Browse treasures

browse_treasures
Read-onlyIdempotent

List treasures of one type, optionally from one lecture or one channel, newest lectures first, with paging. 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

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": {
      "type": "<type>"
    },
    "name": "browse_treasures"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
limitNo
offsetNo
channel_idNoa channel id from list_channels
lecture_idNoa lecture id (YouTube video id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 the safety profile is covered. The description adds genuinely new behavioral facts beyond that: results are ordered newest lectures first, and results are paged. It still doesn't say what a returned treasure record contains or what an empty result means, which keeps it short of a 5.

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?

Core behavior is front-loaded in a single opening sentence, and the type glossary follows as a compact semicolon-delimited list. The glossary is long but each entry earns its place because the enum tokens are opaque without it. Minor redundancy in restating enum names alongside their meanings.

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 five-parameter, read-only, no-output-schema listing tool, the definition covers selection logic, filters, sort order, and paging. The remaining gap is return-shape information, which the absence of an output schema makes slightly more costly, but the essential calling information is present.

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

Parameters4/5

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

Schema description coverage is only 40%, so the description needs to compensate, and it largely does: the ten enum values of 'type' are each glossed with a real definition, and the lecture/channel filters are explained in prose. Paging is mentioned but limit bounds and offset semantics are left entirely to the schema.

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 and resource ('List treasures') plus the scoping model: one required type, optional lecture or channel narrowing. The type glossary makes the resource concrete. It does not explicitly name search_treasures as the contrasting tool, so the browse-vs-search split is only implied by the verb.

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?

The phrase 'optionally from one lecture or one channel' tells the agent which filters exist, and 'one type' implies this is a browse-by-category operation rather than a keyword search. However there is no explicit when-to-use versus search_treasures, no statement about whether lecture_id and channel_id can be combined, and no exclusions.

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