Skip to main content
Glama
This connector has been deprecated

Narrator biography

shamela_get_narrator
Read-onlyIdempotent

ترجمة الراوي

The full dossier on one narrator: name and lineage, death year, ṭabaqa (generation per Taqrīb al-Tahdhīb), Ibn Ḥajar's and al-Dhahabī's grades, kunya/nasab/cities/relations, and — the heart of it — al-jarḥ wa-l-taʿdīl: the critics' verdicts, grouped by critic, each quoted verbatim WITH the book and volume/page it came from (e.g. «تهذيب التهذيب (1/ 101)»). Critics are PAGED (limit, default 10, and offset), because a heavily-documented narrator has dozens — al-Zuhrī has 56 critics and 184 verdicts — and the response reports total_critics/total_verdicts plus a cursor so you can tell a page from the whole file and reach the rest. 15,160 of the 18,989 narrators carry verdicts, from 2,821 named critics. Also returns hadith_notes (فوائد) on audition, irsāl and implicit tawthīq — the evidence for whether a chain is connected. With include_network (default true) it adds the transmission network computed live from the isnād index: how many chains name this narrator, in which of the ten indexed books, and their most frequent teachers (narrates_from) and students (narrates_to) with counts. Quote the verdicts as the critics worded them; do NOT synthesize a grade the register does not state. Get the id from shamela_search_narrators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many CRITICS of al-jarḥ wa-l-taʿdīl to return (1-100, default 10) — the only part of the dossier that is paged. al-Zuhrī has 56 critics and 184 verdicts; they do not fit one response, and `total_critics` says how many there are.
top_nNoHow many teachers and how many students to return, most frequent first (1-100, default 15).
offsetNoCritics to skip, for paging through the verdicts. Follow `next_offset` until `has_more` is false.
narrator_idYesThe narrator id, as returned by shamela_search_narrators or inside a chain from shamela_get_isnad.
include_networkNoInclude the transmission network computed from the isnād index: how many chains this narrator carries, in which books, and their most frequent teachers and students. Set false to skip it when you only need the biography.
response_formatNoOutput format for the human-readable text. 'markdown' (default) is best for direct display; 'json' returns the same data as a single JSON code block; 'none' skips the rendered text entirely and returns a one-line pointer, leaving `structuredContent` as the whole answer. The structured data is returned in `structuredContent` regardless of this setting, so a caller that parses it should pass 'none' — the character budget is measured over BOTH channels, and the unread copy is otherwise spending most of it. Requires the 'response_format.none' capability (see shamela_brief).markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations carry the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial behavior beyond them: the critics list is paged with a cursor, total_critics/total_verdicts let you tell a page from the whole file, the network is computed live from the isnād index, and response_format.none requires a capability. This is unusually rich disclosure.

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 content is dense but front-loaded, with the core dossier contents stated before operational details. It is long (a single sprawling paragraph) and includes some illustrative statistics, but nearly every sentence carries deciding information for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 still describes the return shape adequately: the dossier fields, the verdict grouping by critic with citations, and the network fields (narrates_from/narrates_to with counts). Nothing essential for correct invocation appears missing.

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 coverage is 100%, so the baseline is 3. The description still adds meaning: it flags that critics are the only paged section, explains the cursor/total semantics, and clarifies that total_critics lets the caller distinguish a page from the full file — context the schema does not carry.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb+resource ('the full dossier on one narrator') and enumerates what the dossier contains — lineage, death year, ṭabaqa, grades, kunya/nasab/cities, and al-jarḥ wa-l-taʿdīl verdicts. It is clearly distinguishable from shamela_search_narrators, which it explicitly points to for id acquisition.

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?

Gives clear operational guidance: get the id from shamela_search_narrators, quote verdicts verbatim rather than synthesizing a grade, and set include_network=false when only the biography is needed. It lacks an explicit 'when not to use this vs. X' routing statement, but the id-sourcing prerequisite is spelled out.

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