Skip to main content
Glama

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

Get a lecture's transcript

get_transcript
Read-onlyIdempotent

The lecture's words in order, as numbered segments with start/end seconds (paged). Machine transcription, corrected in places. Use segment numbers from other results to read the context around a passage.

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

Input Schema

NameRequiredDescriptionDefault
countNo
lecture_idYes
from_segmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely useful non-annotation context: the content is machine transcription 'corrected in places,' warning the agent about fidelity, and that results are paged. It does not describe paging limits or ordering guarantees beyond 'in order.'

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 tight sentences: the return shape is front-loaded, the transcription caveat follows, and the usage hint closes. Every clause carries information and nothing is padded.

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 description does the work of explaining the returned segments and their timestamps, which is the key thing an agent needs. The remaining gap is parameter mechanics (defaults, maximum count, offset semantics), which are left entirely to an undocumented schema.

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 all three parameters (lecture_id, count, from_segment) are undocumented structurally. The description partially compensates by implying paging via segment numbers, but never explains that from_segment selects the starting offset, that count defaults to 80 with a 200 cap, or that lecture_id is required. Some meaning is added, but the gap is only partly closed.

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 precisely ('The lecture's words in order, as numbered segments with start/end seconds') and specifies the return shape including pagination. It is clear what the tool yields, though the verb is implicit and it does not explicitly distinguish itself from siblings like get_lecture or search_lectures.

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?

It gives a concrete usage pattern: 'Use segment numbers from other results to read the context around a passage.' That tells the agent when this tool is the right follow-up call. It stops short of stating exclusions or naming which sibling results supply those segment numbers, so the guidance is contextual rather than exhaustive.

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