Skip to main content
Glama

list_translations

Retrieve available Quran translations to access different interpretations of Islamic scripture for study and understanding.

Instructions

List all available Quran translations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that executes the list_translations tool by mapping and returning available translations from the TRANSLATIONS constant.
    /**
     * List available translations
     */
    export function listTranslations() {
      return TRANSLATIONS.map(t => ({
        slug: t.slug,
        name: t.name,
        language: t.language,
      }));
    }
  • Defines the tool schema for list_translations, specifying no input parameters are required.
    {
      name: 'list_translations',
      description: 'List all available Quran translations.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Registers the list_translations tool in the executor switch case, invoking the handler function.
    case 'list_translations': {
      result = listTranslations();
      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. It states a read operation ('List') but doesn't disclose behavioral traits such as whether it requires authentication, has rate limits, returns paginated results, or what the output format is. This is a significant gap 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 directly states the tool's purpose without any waste. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 no annotations, no output schema, and a simple list operation, the description is incomplete. It doesn't explain what 'available' means, how results are returned, or any limitations, which could confuse an agent trying to use it effectively.

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 no parameter documentation is needed. The description doesn't add param info, but that's acceptable here. Baseline is 4 for zero parameters, as the schema fully covers the lack of inputs.

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 resource ('all available Quran translations'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_reciters' or 'list_tafsir_sources', which list other resources, so it misses full sibling distinction.

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. It doesn't mention prerequisites, context for use, or compare to siblings like 'list_surahs' or 'list_hadith_collections', leaving the agent with no usage direction.

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