Skip to main content
Glama

search_narrators

Read-only

Find narrators by name to get the narrator_id required by other hadith tools. Results are paginated; broaden the name phrase if nothing matches.

Instructions

Find narrators by name, to get the narrator_id the other tools take.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPart of the narrator's name, matched as one phrase (e.g. «الزهري»). If nothing matches, try fewer words.
limitNoResults per page, 1 to 50.
offsetNoResults to skip: 0 for the first page, then the previous response's next_offset.

Output Schema

NameRequiredDescriptionDefault
totalYesHow many narrators match, across all pages.
offsetYesHow many narrators this page skipped.
resultsYes
next_offsetNoPass as offset for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 the safety profile is covered. The description adds the downstream-purpose context but says nothing extra about matching behaviour, empty-result handling, or paging beyond what the schema already documents. Adequate, but no value added beyond structured fields.

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?

A single short sentence with zero waste: it front-loads the action and resource and then states the downstream use. Nothing is repeated from the schema or annotations.

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 an output schema, fully documented parameters, and read-only annotations, the description only needs to establish purpose and routing, which it does. It could be slightly stronger by hinting at what an empty result means, but nothing essential is missing.

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 description coverage is 100%, so name matching, the 1-50 limit, and the offset/next_offset paging convention are all fully documented in the schema. The description contributes no additional parameter meaning, which matches the baseline 3 when the schema does the heavy lifting.

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?

States a specific verb ('Find') and resource ('narrators') plus the scoping constraint ('by name'), and names the payoff (the narrator_id other tools take), which implicitly distinguishes it from get_narrator's id-based lookup. It does not explicitly name a sibling, so it stops short of full differentiation.

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?

'to get the narrator_id the other tools take' gives a clear reason to select this tool: resolving a name to an identifier before calling the retrieval tools. There is no explicit when-not guidance or named alternative for name-based vs id-based lookup, leaving that inference to the agent.

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