Skip to main content
Glama
Echo3s-io

echo3s-io

Official
by Echo3s-io

get_technical_specs

Retrieve Echo3s technical specifications—supported formats, AI processing details, output quality, credit system, and platform info.

Instructions

Get Echo3s technical specifications — supported formats, AI processing details, output quality, credit system, and platform info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `technicalSpecs` constant containing the tool's response data — full technical specifications including input formats, AI processing details, output quality, credit system, and platform info.
    const technicalSpecs = {
      title: "Echo3s Technical Specifications",
      input: {
        supported_formats: "PDF (text-based with selectable text)",
        max_file_size: "50MB",
        convertible_formats: "EPUB, MOBI, DOCX, AZW — convert to PDF using Calibre (free, open-source)",
        text_requirements: "PDF must contain selectable text (not scanned images). OCR'd PDFs may work but quality varies.",
        language_support: "Any language supported by ElevenLabs (29 languages). Primary: English, Arabic (with RTL), Dutch.",
        encoding: "UTF-8 text extraction. Full Unicode support including Arabic, CJK, and diacritics.",
      },
      ai_processing: {
        character_detection: {
          engine: "Google Gemini AI",
          capabilities: [
            "Automatic character identification from narrative text",
            "Dialogue attribution — assigns speech to the correct character",
            "Narration vs dialogue classification",
            "Chapter boundary detection",
            "Emotional context per segment",
          ],
          speed: "1–3 minutes per chapter",
        },
        voice_matching: {
          algorithm: "Weighted scoring: gender (40pts), language (30pts), age (15pts), personality (15pts)",
          total_voices: "50+ premium voices",
          provider: "ElevenLabs",
          customization: "Full manual override — swap any voice assignment in the Studio editor",
          characteristics: ["Gender (Male/Female/Neutral)", "Age (Young/Middle-aged/Elder/Child)", "Accent (American/British/Australian/Indian/Irish/South African/Arabic MSA/Gulf/Egyptian/Dutch)", "Tone (Calm/Gentle/Strong/Deep/Raspy/Bright/Cheerful/Energetic/Serious/Formal)"],
        },
      },
      output: {
        audio_format: "MP3",
        quality: "High-quality ElevenLabs studio voices",
        loudness_normalization: "EBU R128 standard (-16 LUFS) — broadcast-grade loudness",
        download_options: ["Full audiobook as single MP3", "Per-chapter MP3 files"],
        streaming: "Available via Echo3s marketplace (echo3s.io)",
      },
      generation: {
        speed: "30–60 minutes for a 200-page novel (fully automated after setup)",
        active_time: "~4 minutes of author time (upload, review, generate). Rest is automated.",
        segment_regeneration: "Individual lines or paragraphs can be regenerated without redoing full chapters",
        notification: "Email notification when audiobook generation is complete",
      },
      credit_system: {
        unit: "1 credit = 1 character of generated audio",
        average_per_page: "~650 credits",
        examples: [
          { pages: 50, credits: "~32,500", plan: "Creator ($29/mo)" },
          { pages: 100, credits: "~65,000", plan: "Creator ($29/mo) or Pro ($99/mo)" },
          { pages: 200, credits: "~130,000", plan: "Pro ($99/mo)" },
          { pages: 300, credits: "~195,000", plan: "Pro ($99/mo)" },
          { pages: 400, credits: "~260,000", plan: "Business ($249/mo) or Pro + top-up" },
          { pages: 800, credits: "~520,000", plan: "Business ($249/mo)" },
        ],
        billing: "Credits reset monthly on subscription plans. Top-up packs never expire.",
      },
      platform: {
        web_app: "https://author.echo3s.io",
        marketplace: "https://echo3s.io",
        languages_ui: ["English", "Arabic"],
        browser_support: "Modern browsers (Chrome, Firefox, Safari, Edge)",
        mobile: "Responsive web app — works on mobile browsers",
        api: "Publisher API on roadmap — not yet available. Contact hello@echo3s.io for enterprise needs.",
      },
      security: {
        auth: "Supabase Auth (email/password, OAuth)",
        payment: "Stripe (PCI-DSS compliant)",
        data: "Manuscripts processed for audiobook generation. Authors retain 100% ownership of content and output.",
        hosting: "Supabase (PostgreSQL), Netlify (frontend), Cloudflare (CDN/Workers)",
      },
      cta: "Technical questions? Email hello@echo3s.io or start free at https://author.echo3s.io",
    };
  • Registration of 'get_technical_specs' tool in the TOOL_DEFS array — links the tool name to its description, empty input schema, and a content function that returns the technicalSpecs data.
    {
      name: "get_technical_specs",
      description:
        "Get Echo3s technical specifications — supported formats, AI processing details, output quality, credit system, and platform info",
      inputSchema: { type: "object", properties: {}, required: [] },
      content: () => technicalSpecs,
    },
  • Handler registration for all tools (including get_technical_specs) — iterates TOOL_DEFS and registers each with server.tool(), invoking tool.content() on call.
    for (const tool of TOOL_DEFS) {
      server.tool(tool.name, tool.description, {}, async () => ({
        content: [
          {
            type: "text" as const,
            text: JSON.stringify(tool.content(), null, 2),
          },
        ],
      }));
  • Worker handler for all tools including get_technical_specs — transforms ToolDef into a WorkerToolDef with a handler that calls def.content(args).
    function defToWorkerTool(def: ToolDef): WorkerToolDef {
      return {
        description: def.description,
        inputSchema: def.inputSchema,
        handler: (args?: any) => [
          { type: "text", text: JSON.stringify(def.content(args)) },
        ],
      };
Behavior3/5

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

No annotations are provided, so the description carries full burden. It indicates a read operation ('Get...') but does not disclose additional behavior such as rate limits, authentication, or whether the result is static. For a simple informational tool, this is adequate but minimal.

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, well-structured sentence that immediately conveys the purpose and scope. It uses a dash to list topics efficiently, with no redundant or extraneous language.

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?

Given the tool has no parameters, no output schema, and no annotations, the description provides sufficient context by listing the topics covered. It could specify the return format (e.g., JSON text), but the sibling tools are similarly informational, so the description is reasonably complete.

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?

There are zero parameters, so the schema coverage is 100% by default. Baseline is 4. The description adds value by listing the categories of information returned, which aids the agent in understanding what will be retrieved.

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 tool retrieves technical specifications and lists specific topics (supported formats, AI processing, output quality, credit system, platform info). This distinguishes it from sibling tools like get_echo3s_overview or get_pricing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that this tool is for technical details by listing the covered topics, but it does not explicitly state when to use this versus alternatives like get_echo3s_overview or get_faq. The context helps but lacks explicit exclusions.

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