Skip to main content
Glama

list_hadith_collections

Retrieve available Hadith collections to access Islamic traditions and scholarly interpretations for research or study purposes.

Instructions

List all available Hadith collections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that executes the tool logic, returning a list of Hadith collections with their slug, name, and total number of hadiths by mapping from the HADITH_COLLECTIONS constant.
    export function listHadithCollections() {
      return HADITH_COLLECTIONS.map(collection => ({
        slug: collection.slug,
        name: collection.name,
        totalHadiths: collection.totalHadiths,
      }));
    }
  • The MCP tool schema definition specifying the tool name, description, and input schema (no parameters required).
    {
      name: 'list_hadith_collections',
      description: 'List all available Hadith collections.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Registration in the tool executor switch statement that dispatches calls to the listHadithCollections handler function.
    case 'list_hadith_collections': {
      result = listHadithCollections();
      break;
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'List all available Hadith collections', which implies a read-only operation, but doesn't specify if it's paginated, returns structured data, or has any limitations. For a tool with zero annotation coverage, this is insufficient to inform the agent about its behavior.

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?

The description is a single, clear sentence: 'List all available Hadith collections.' It is front-loaded, efficient, and wastes no words, making it highly concise and well-structured for its simple purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on output format or behavioral traits. Without annotations or an output schema, the agent might be uncertain about the return value, making it incomplete for full contextual understanding.

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?

The input schema has 0 parameters with 100% coverage, so the schema fully documents the absence of inputs. The description adds no parameter information, which is acceptable since there are no parameters to explain. A baseline of 4 is appropriate as the description doesn't need to compensate for any gaps.

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 clearly states the verb 'List' and the resource 'all available Hadith collections', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_surahs' or 'list_tafsir_sources', which follow a similar pattern but for different resources, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. For example, it doesn't mention if this is for browsing collections before using 'get_hadith' or 'search_hadith', or how it relates to other listing tools. This lack of context leaves the agent without clear usage instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Prince77-7/quranMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server