Skip to main content
Glama

get_hadith

Read-only

Retrieve all Sahih al-Bukhari entries that contain a given hadith number, including sanad, matn, tawabi, chains, and all hadith numbers within multi-hadith entries.

Instructions

Get every entry that holds a hadith number: sanad, matn, tawabi and chains.

A number can sit in more than one entry (221, 4952 and 5472 do), and an entry can hold several consecutive hadiths; hadith_numbers lists them all.

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

Input Schema

NameRequiredDescriptionDefault
numberYesThe hadith number, 1 to 7563.

Output Schema

NameRequiredDescriptionDefault
entriesYes
hadith_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's job is supplementary and it delivers: it discloses the non-obvious result cardinality, that one number can resolve to multiple entries and that entries may bundle several consecutive hadiths exposed via hadith_numbers. That is genuine behavioral context beyond the annotations.

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?

Two short sentences with the core behavior front-loaded and the multiplicity caveat second. No filler, no restatement of the title.

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-value explanation is not required, and the description supplies the multiplicity caveat that the schema alone would not convey. What remains missing is any mention of error behavior for an out-of-range or nonexistent number.

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% and the single parameter is fully documented with its 1-7563 range, so the schema already carries the weight. The description adds only illustrative example numbers (221, 4952, 5472) for the duplicate-entry case, not new format or constraint meaning.

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 ('Get every entry that holds a hadith number') and enumerates the returned fields (sanad, matn, tawabi, chains). That is clear enough to distinguish it from search-oriented siblings, but it never names an alternative tool the way a 5 would.

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

Usage Guidelines3/5

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

Usage is only implied: an agent should call this when it already has a hadith number in hand. There is no explicit statement of when to prefer search_hadiths instead, nor any prerequisite or exclusion.

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