Skip to main content
Glama

get_narrator

Read-only

Retrieve a narrator’s name, rank, hadith count, and top teachers and students, ranked by shared hadiths, using a narrator ID from search results.

Instructions

Get a narrator's name, rank, hadith count, and top teachers and students.

Teachers and students are ranked by the hadiths they share with this narrator.

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": {
      "narrator_id": "<narrator_id>"
    },
    "name": "get_narrator"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoTeachers and students to list, each.
narrator_idYesFrom search_narrators.

Output Schema

NameRequiredDescriptionDefault
eraNo
rankNoThe narrator's grade, such as صحابي or ثقة.
kunyaNo
locationNo
studentsYesWho received hadiths from this narrator, most shared hadiths first.
teachersYesWho passed hadiths to this narrator, most shared hadiths first.
full_nameNo
narrator_idYesPass to get_narrator or search_hadiths.
hadith_countYesHadiths this narrator appears in.
name_in_chainYesHow chains usually name this narrator.
student_countYesAll students; `students` lists the strongest `limit`.
teacher_countYesAll teachers; `teachers` lists the strongest `limit`.
scholarly_opinionNoWhat the scholars said of this narrator, summarised.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description still adds real behavioral value by disclosing the ordering rule for teachers/students (ranked by shared hadiths) and implicitly the truncation behavior of the top-N list, though it says nothing about what happens when a narrator_id is not found.

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?

Two short sentences, front-loaded with the returned fields, with the second sentence devoted entirely to the ranking semantics. Nothing is redundant or padded, though the first sentence is a dense list that could be slightly easier to scan.

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?

An output schema exists, so return values needn't be spelled out, yet the description still summarizes them helpfully. For a simple single-entity lookup the coverage is nearly sufficient; the remaining gap is the lack of differentiation from get_narrator_biography and any error/empty-result behavior.

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 100%, so both parameters are already documented, including that limit applies 'each' to teachers and students. The description's phrase 'top teachers and students' corroborates that meaning but adds no syntax, default, or range information beyond the schema, so the baseline 3 applies.

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 uses a specific verb ('Get') plus the resource ('a narrator') and enumerates exactly what comes back: name, rank, hadith count, top teachers and students. That field list separates it from search_narrators, but the description never explicitly distinguishes it from the close sibling get_narrator_biography.

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?

There is no when-to-use or when-not-to-use guidance in the description itself. The only routing hint ('From search_narrators') lives in the schema's narrator_id field, and nothing explains when an agent should pick this over get_narrator_biography or search_narrators.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.