Skip to main content
Glama

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

List lectures

list_lectures
Read-onlyIdempotent

Lectures in the corpus (with a transcript), optionally of one channel or whose title contains some words, newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_lectures"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
channel_idNo
title_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description does add real behavior beyond that: only lectures having a transcript are returned, and results come newest-first. It does not disclose pagination behavior or what fields a lecture record contains.

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 dense sentence with no filler, and the most important information (what the collection is, the transcript restriction) is front-loaded. The compressed phrasing of the optional filters is slightly awkward but not wasteful.

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 simple read-only listing tool with no output schema, the description covers scope, filters, and ordering adequately. The remaining gap is pagination and return-shape detail, which is modest but worth noting given there is no output schema to fall back on.

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 0%, so the description carries the burden and it partially does: channel_id maps to 'of one channel' and title_contains maps to 'title contains some words', including the substring semantics. The two pagination parameters (limit, offset) are never mentioned, so half the parameters get no added meaning.

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?

The description names the resource (lectures in the corpus), states a meaningful scope restriction (only those with a transcript), and lists the supported filters and sort order. It is a clear listing operation, though it never explicitly contrasts itself with search_lectures, which an agent could plausibly confuse it with.

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 implied rather than stated: 'optionally of one channel or whose title contains some words' tells the agent that channel and title filtering are available, and 'newest first' hints at browse-style enumeration. There is no explicit when-to-use, when-not, or pointer to search_lectures for full-text queries, so the agent must infer the choice.

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