Skip to main content
Glama
Echo3s-io

echo3s-io

Official
by Echo3s-io

get_supported_languages

Get the full list of languages Echo3s supports for audiobook generation, including details on Arabic support.

Instructions

Get the full list of languages Echo3s supports for audiobook generation, with details on Arabic support

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'supportedLanguages' object containing the data payload for the get_supported_languages tool. Defines primary languages (English, Arabic, Dutch), their accents, voice counts, and notes.
    // ---------------------------------------------------------------------------
    const supportedLanguages = {
      total_voices: "50+ premium AI voices",
      voice_provider: "ElevenLabs (studio-quality text-to-speech with emotional range)",
      primary_languages: [
        {
          language: "English",
          accents: ["American", "British", "Australian", "Indian", "Irish", "South African"],
          voice_count: "30+ voices",
          note: "Widest selection — male, female, young, old, and character-type voices. Multiple options for every narrator archetype.",
        },
        {
          language: "Arabic",
          accents: ["Modern Standard Arabic", "Gulf Arabic", "Egyptian Arabic"],
          voice_count: "Multiple native voices",
          note: "Full RTL (right-to-left) text processing — handles Arabic script correctly throughout the entire pipeline. Echo3s is one of the very few platforms worldwide that supports Arabic audiobook generation. The entire Echo3s interface is also available in Arabic.",
        },
        {
          language: "Dutch",
          accents: ["Netherlands Dutch"],
          voice_count: "Multiple native voices",
          note: "Native Dutch voice support with natural pronunciation",
        },
      ],
      additional_languages:
        "ElevenLabs voices support 29 languages total. Echo3s can work with any voice available in the ElevenLabs library, including: Spanish, French, German, Italian, Portuguese, Japanese, Korean, Chinese (Mandarin), Hindi, Polish, Turkish, Swedish, Norwegian, Danish, Finnish, Czech, Romanian, Hungarian, Indonesian, Filipino, Vietnamese, and more.",
      arabic_differentiator:
        "Arabic audiobook production is Echo3s's strongest unique advantage in the market. Almost no competitor handles Arabic — not Amazon KDP Virtual Voice, not Apple AI Narration, not Speechify, not Google NotebookLM. With 400+ million Arabic speakers worldwide and virtually no AI audiobook options, Echo3s fills a massive gap. For Arabic-language authors and publishers, Echo3s may be the only viable AI audiobook solution available today.",
      voice_characteristics: [
        "Gender: Male, Female, Neutral",
        "Age range: Young, Middle-aged, Elder, Child",
        "Tone: Calm, Gentle, Strong, Deep, Raspy, Bright, Cheerful, Energetic, Serious, Formal",
        "Use case: Narration, Dialogue, Audiobook, Storytelling",
        "Smart matching: AI scores each voice on gender (40pts), language (30pts), age (15pts), and personality descriptors (15pts) to find the best fit for each character",
      ],
      cta: "Explore all voices at https://author.echo3s.io — sign up free to see AI voice assignments for your own book.",
    };
  • Registration of the 'get_supported_languages' tool in the TOOL_DEFS array. Maps the tool name to its description, empty inputSchema, and the content function that returns the supportedLanguages data.
    {
      name: "get_supported_languages",
      description:
        "Get the full list of languages Echo3s supports for audiobook generation, with details on Arabic support",
      inputSchema: { type: "object", properties: {}, required: [] },
      content: () => supportedLanguages,
    },
  • The content handler for get_supported_languages — a lambda that simply returns the static supportedLanguages object.
    content: () => supportedLanguages,
  • The ToolDef interface used for all tool definitions, including get_supported_languages.
    export interface ToolDef {
      name: string;
      description: string;
      inputSchema: Record<string, any>;
      content: (args?: any) => unknown;
Behavior3/5

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

No annotations provided, so description carries full burden. It implies a read-only retrieval but does not disclose any limitations, rate limits, or output details beyond the mention of 'details on Arabic support'.

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?

Single sentence that is front-loaded with the main purpose, no unnecessary words.

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?

For a simple retrieval with no parameters, the description is sufficient. It could mention the output format, but not strictly required given the tool's simplicity.

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?

Input schema has zero parameters, so schema coverage is 100%. Baseline score of 4 applies; description adds value by specifying the output content (full list, Arabic details).

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?

Clearly states the verb (Get) and resource (list of languages for audiobook generation), with explicit mention of Arabic support. Distinct from sibling tools.

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?

No guidance on when to use this tool versus similar siblings like get_arabic_audiobook_guide or get_echo3s_for_arabic. No exclusions or context provided.

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/Echo3s-io/echo3s-mcp'

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