Skip to main content
Glama

list_tafsir_sources

Discover available Tafsir commentary sources with their languages and authors to access scholarly interpretations of Quranic texts.

Instructions

List all available Tafsir (commentary) sources with their languages and authors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that executes the tool logic by returning a mapped list of available Tafsir sources from the TAFSIR_SOURCES constant.
    export function listTafsirSources() {
      return TAFSIR_SOURCES.map(source => ({
        slug: source.slug,
        name: source.name,
        language: source.language,
        author: source.author,
      }));
    }
  • The tool definition in the tools array, including name, description, and empty input schema (no parameters required).
    {
      name: 'list_tafsir_sources',
      description: 'List all available Tafsir (commentary) sources with their languages and authors.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • The switch case registration in the executeTool function that calls the listTafsirSources handler when the tool is invoked.
    case 'list_tafsir_sources': {
      result = listTafsirSources();
      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. While 'List all available' suggests a read-only operation, the description doesn't mention important behavioral aspects like whether the list is paginated, sorted, or filtered; whether it requires authentication; what format the output takes; or if there are rate limits. This leaves significant gaps for a tool with zero annotation coverage.

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, efficient sentence that communicates the essential purpose without any wasted words. It's front-loaded with the core action and resource, and the parenthetical '(commentary)' provides helpful clarification. Every element serves a clear 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 simplicity (no parameters, no output schema, no annotations), the description is adequate but incomplete. It explains what the tool does but lacks behavioral context about how it works (format, pagination, authentication needs). For a list operation with zero structured metadata, more behavioral disclosure would be beneficial to fully inform the agent.

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 tool has zero parameters, and schema description coverage is 100% (since there are no parameters to document). The description appropriately doesn't discuss parameters, which is correct for a parameterless tool. No additional parameter semantics are needed beyond what the empty schema already indicates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('List all available'), resource ('Tafsir (commentary) sources'), and scope ('with their languages and authors'). It distinguishes this tool from siblings like 'get_tafsir' (which retrieves specific commentary content) and 'list_translations' (which lists translations rather than commentary sources).

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?

The description implies usage context (when you need to know what commentary sources exist), but doesn't explicitly state when to use this versus alternatives. For example, it doesn't clarify if this should be used before 'get_tafsir' to identify available sources, or if there are prerequisites like authentication. The guidance is functional but not comprehensive.

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