Skip to main content
Glama

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

Get a lecture

get_lecture
Read-onlyIdempotent

A lecture's details: title, channel, length, series it belongs to, its topics with their summaries, and how many treasures of each type it holds. Use get_transcript for its words.

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": {
      "lecture_id": "<lecture_id>"
    },
    "name": "get_lecture"
  }
}

Input Schema

NameRequiredDescriptionDefault
lecture_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. Beyond that, the description discloses the returned data shape in detail — including nested topic summaries and per-type treasure counts — which is valuable since there is no output schema. It does not mention error behavior for unknown ids, but that is a minor gap against the annotation coverage.

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?

Two short sentences with zero filler, and the payload description is front-loaded before the sibling pointer. Every clause adds information an agent would otherwise lack.

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?

With no output schema, the field enumeration is exactly what the description needs to supply, and it does so thoroughly. The remaining hole is the single input parameter's provenance, which is the one thing an agent cannot infer and which the description omits.

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%: lecture_id has no documented format, source, or example. The description spends its words on return contents and never compensates for that gap, so an agent still has to guess what a valid lecture_id looks like and how to obtain one.

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 enumerates the exact resource contents (title, channel, length, series, topics with summaries, treasure counts), which makes the retrieval purpose unmistakable even though the sentence has no verb of its own. It also explicitly separates this tool from get_transcript, so an agent can distinguish it from the closest sibling without opening the schema.

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?

It gives one concrete routing rule: 'Use get_transcript for its words', which is genuinely useful disambiguation. However, it says nothing about the prerequisite for this tool — where a lecture_id comes from (search_lectures / list_lectures) — nor when to prefer get_topic or get_treasure, leaving the main selection decision implicit.

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