Skip to main content
Glama

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

Get a topic

get_topic
Read-onlyIdempotent

A topic of the map with the lecture passages filed under it (each with its summary, lecture and link).

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": {
      "topic_id": "<topic_id>"
    },
    "name": "get_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
topic_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

The annotations already establish that this is a safe read-only, idempotent lookup, and the description adds useful return-shape context: the topic contains lecture passages, each with a summary, lecture, and link. It does not explain pagination or how the limit parameter affects results.

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?

The definition is a single efficient sentence with no wasted wording, and the core return contents are front-loaded. It is a noun phrase rather than an action statement, so it is slightly less immediately actionable than an explicit retrieval description.

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 simple two-parameter getter with no output schema, the description partially covers the return shape by naming the contained passages and fields. However, it omits the limit parameter and pagination behavior, so an agent lacks important invocation context.

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%, and the description does not explain topic_id or limit. It only gives general context about a topic containing passages, leaving the limit parameter and its default/maximum behavior entirely undocumented.

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 identifies the resource as a topic of the map and specifies that it includes lecture passages filed under it with summaries, lecture references, and links. The tool name and title supply the retrieval verb, but the description does not differentiate this getter from siblings such as search_topics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives no explicit guidance on when to use this tool versus search_topics or the other retrieval tools. There is no mention of prerequisites, expected inputs, or exclusions, so the agent must infer usage from the name alone.

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