Skip to main content
Glama

get_quran_verse

Retrieve Quran verses with Arabic text and English translation by specifying surah and ayah numbers. Access multiple translation options for studying Islamic texts.

Instructions

Get a Quran verse with both Arabic text and English translation. Returns the specified verse from the Quran.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
surahYesSurah number (1-114)
ayahYesAyah (verse) number within the surah
translationNoTranslation to use (default: en.asad). Options: en.asad, en.sahih, en.pickthall, en.yusufali, en.hilalien.asad

Implementation Reference

  • The main handler function that fetches both Arabic text and English translation for the specified Quran verse using helper functions getQuranArabic and getQuranTranslation.
    export async function getQuranVerse(
      surah: number,
      ayah: number,
      translationSlug: string = 'en.asad'
    ): Promise<{ arabic: QuranVerse; translation: QuranVerse }> {
      const [arabic, translation] = await Promise.all([
        getQuranArabic(surah, ayah),
        getQuranTranslation(surah, ayah, translationSlug),
      ]);
    
      return { arabic, translation };
    }
  • Defines the tool name, description, and input schema (parameters: surah, ayah, optional translation) for get_quran_verse.
      name: 'get_quran_verse',
      description: 'Get a Quran verse with both Arabic text and English translation. Returns the specified verse from the Quran.',
      inputSchema: {
        type: 'object',
        properties: {
          surah: {
            type: 'number',
            description: 'Surah number (1-114)',
            minimum: 1,
            maximum: 114,
          },
          ayah: {
            type: 'number',
            description: 'Ayah (verse) number within the surah',
            minimum: 1,
          },
          translation: {
            type: 'string',
            description: 'Translation to use (default: en.asad). Options: en.asad, en.sahih, en.pickthall, en.yusufali, en.hilali',
            default: 'en.asad',
          },
        },
        required: ['surah', 'ayah'],
      },
    },
  • The switch case in the tool executor that destructures arguments and calls the getQuranVerse handler function to execute the tool.
    case 'get_quran_verse': {
      const { surah, ayah, translation = 'en.asad' } = args;
      result = await getQuranVerse(surah, ayah, translation);
      break;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns a verse with Arabic text and English translation, but does not mention potential rate limits, authentication needs, error handling, or output format details. This is a significant gap for a tool with no structured safety or behavioral hints.

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?

The description is concise and front-loaded, consisting of two sentences that directly state the tool's function and return. There is no wasted verbiage, and it efficiently communicates the core purpose, though it could be slightly more structured by explicitly separating purpose from behavioral details.

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

Completeness2/5

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

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is incomplete. It lacks details on output format, error cases, or behavioral constraints, which are crucial for an AI agent to invoke the tool correctly. The high schema coverage helps, but the description does not compensate for missing behavioral and output context.

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?

The input schema has 100% description coverage, clearly documenting all parameters (surah, ayah, translation) with constraints and options. The description adds minimal value beyond the schema by implying the tool uses these parameters to fetch a verse, but does not provide additional semantic context or usage examples. Baseline 3 is appropriate given high schema coverage.

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 tool's purpose as retrieving a Quran verse with Arabic text and English translation, specifying the verb 'Get' and resource 'Quran verse'. It distinguishes from siblings like get_random_verse by indicating it returns a specified verse, but does not explicitly contrast with get_full_surah or get_surah_info, which are related but not direct alternatives.

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 such as get_random_verse, get_full_surah, or search_quran. It mentions returning a specified verse, which implies usage for exact verse retrieval, but lacks explicit when-to-use or when-not-to-use statements, leaving the agent to infer context from sibling tool names.

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