Skip to main content
Glama

get_narrator_biography

Read-only

Retrieve classical biographical source entries for a narrator to understand their life and reliability, organized source by source.

Instructions

Get what the classical books of tarajim say about a narrator, source by source.

Long: call it only when the user asks about the narrator's life or reliability.

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

Input Schema

NameRequiredDescriptionDefault
narrator_idYesFrom search_narrators.

Output Schema

NameRequiredDescriptionDefault
urlYesThe narrator's page on bukhari-pedia.net, to cite.
sourcesYesWhat each book of tarajim says about the narrator, in full.
narrator_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful context about the data's provenance (classical biographical dictionaries, reported per source), which an agent would not infer from the annotations, but it says nothing about coverage gaps, missing narrators, or entry length.

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 with the core purpose front-loaded and the usage constraint second; nothing is wasted. The literal 'Long:' tag before the constraint is a slightly awkward artifact but does not obscure the content.

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 a single required parameter, full schema coverage, an output schema, and read-only annotations, most structured burden is already carried elsewhere. The description supplies the domain provenance and the trigger condition, leaving little an agent needs in order to call it correctly.

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%; the schema itself documents narrator_id and that it comes from search_narrators. The description adds no further meaning about the identifier, so the baseline of 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 names a specific verb and resource: retrieving what classical tarajim books say about a narrator, explicitly 'source by source', which tells an agent the return is per-source biographical material rather than a single summary. It is distinguishable from the sibling get_narrator, which by name alone is not a biography lookup, though the description never says so outright.

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 an explicit trigger condition: call it only when the user asks about the narrator's life or reliability. That is a real when-to-use rule with an implied when-not, but no sibling alternative is named for the cases where the user wants identity or hadith data instead.

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