Bayan — Islamic encyclopedia (Arabic)

حديث

get_hadith

Read-only

A hadith by book and its number as cited (e.g. Sahih al-Bukhari 1 = «إنما الأعمال بالنيات»), or by seq from a search result or a site link: its text, grade, takhrij (where known), narrators, related Bayan articles and the link to its page.

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

Input Schema

Name	Required	Description
`seq`	No	Alternatively, its place in the book (the `seq` of search results and site links)
`book`	Yes	Book slug: sahih-al-bukhari, sahih-muslim, sabil-al-rashad, sunan-abi-dawud, jami-al-tirmidhi, sunan-al-nasai, sunan-ibn-majah, musnad-ahmad, al-muwatta
`number`	No	The hadith's number in the book, as it is cited

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only and closed-world behavior; the description adds that the response includes text, grade, takhrij where known, narrators, related articles, and a page link. It does not cover error behavior or precedence, but it adds meaningful output-side 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence front-loads the lookup modes before listing return fields. It is dense but contains no filler; a slightly clearer split between input and output would improve readability.

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 full schema coverage, annotations, and no output schema, the description supplies the missing return-value context and an example. It leaves some ambiguity about precedence when both number and seq are supplied and whether book is always required, so it is not fully complete.

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 adds a concrete cited-number example and clarifies seq as the search-result/site-link position. It does not add much beyond the schema's parameter descriptions, but the example is useful.

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 identifies the resource (a hadith) and the two lookup modes (book+number or seq), plus what is returned. It does not explicitly name a verb or route against siblings like get_article or get_narrator, but the hadith resource is clearly distinct.

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?

It explains that seq can come from a search result or site link, which helps identify valid inputs. It does not say when to use this tool instead of search or the other get_* tools, nor when not to use it.

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

All Bayan — Islamic encyclopedia (Arabic) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?