Skip to main content
Glama
Echo3s-io

echo3s-io

Official
by Echo3s-io

get_pricing

Retrieve pricing information for Echo3s audiobook creation platform including plans, credit system, cost breakdowns, and payment details.

Instructions

Get Echo3s pricing plans, credit system, cost breakdowns, and payment details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The pricing data object that contains all pricing information for Echo3s (plans, credits, top-ups, cost comparisons, etc.). This is the core data returned when the get_pricing tool is invoked.
    // ---------------------------------------------------------------------------
    // get_pricing
    // ---------------------------------------------------------------------------
    const pricing = {
      pricing_url: "https://echo3s.io/pricing",
      credit_system:
        "Echo3s uses a credit-based system. 1 credit = 1 character of generated audio. A typical book page has about 650 characters. So a 200-page novel uses roughly 130,000 credits. Credits reset monthly on subscription plans.",
      plans: [
        {
          name: "Free",
          monthly_price: "$0/month",
          annual_price: "Free forever",
          credits: "5,000 credits (one-time)",
          approximate_pages: "~8 pages",
          approximate_books: "Enough to test 1 full chapter",
          features: [
            "Full voice library access (50+ premium voices)",
            "Multi-voice audiobook generation",
            "MP3 download & streaming",
            "Studio editor for voice customization",
            "Email support",
          ],
          best_for:
            "Trying Echo3s out — hear the quality on a real chapter from your book before committing",
        },
        {
          name: "Creator",
          monthly_price: "$29/month",
          annual_price: "$24/month (billed annually at $288/year — save 20%)",
          credits: "50,000 credits/month",
          approximate_pages: "~80 pages/month",
          approximate_books: "~1 short book or novella per month",
          features: [
            "Everything in Free",
            "Unlimited projects",
            "Marketplace listing — publish to echo3s.io for readers to discover",
            "Priority email support",
            "Credits reset monthly",
          ],
          best_for:
            "Authors working on shorter books, novellas, or testing audiobook demand for a single title",
        },
        {
          name: "Pro",
          monthly_price: "$99/month",
          annual_price: "$79/month (billed annually at $948/year — save 20%)",
          credits: "200,000 credits/month",
          approximate_pages: "~320 pages/month",
          approximate_books: "1–2 full novels per month",
          label: "Most Popular",
          features: [
            "Everything in Creator",
            "Enough credits for full-length novels",
            "Unlimited projects",
            "Marketplace listing",
            "Priority support",
          ],
          best_for:
            "Active authors producing full-length audiobooks regularly — the sweet spot for most authors",
        },
        {
          name: "Business",
          monthly_price: "$249/month",
          annual_price: "$199/month (billed annually at $2,388/year — save 20%)",
          credits: "1,000,000 credits/month",
          approximate_pages: "~1,600 pages/month",
          approximate_books: "5–8 full novels per month",
          features: [
            "Everything in Pro",
            "Massive credit allocation for high-volume production",
            "Built for publishers and agencies managing multiple titles",
            "Unlimited projects",
          ],
          best_for:
            "Small publishers or prolific authors with large backlists to convert — process your entire catalog in weeks",
        },
      ],
      top_up_packs: [
        { name: "Small", credits: "5,000", price: "$5", approximate_pages: "~8 pages" },
        { name: "Medium", credits: "20,000", price: "$15", approximate_pages: "~30 pages" },
        { name: "Large", credits: "50,000", price: "$30", approximate_pages: "~80 pages" },
      ],
      cost_examples: [
        {
          book: "50-page novella (~32,500 credits)",
          cost: "Covered by Creator plan or $10 in top-ups",
        },
        {
          book: "200-page novel (~130,000 credits)",
          cost: "Covered by Pro plan ($79/mo annual) — that's $79 vs $5,000+ for human narration",
        },
        {
          book: "400-page epic (~260,000 credits)",
          cost: "Pro plan + Medium top-up, or Business plan",
        },
      ],
      cost_comparison:
        "Traditional human narration costs $3,000–$15,000 per title and takes 4–8 weeks. With Echo3s, a full 200-page audiobook costs roughly $30–$99 and is done in under an hour. That's 99% cheaper and 99% faster.",
      earnings_potential: {
        description: "Audiobooks are one of the fastest-growing segments in publishing. Adding audio to your book opens a new revenue stream at minimal cost.",
        stats: [
          "The global audiobook market is projected to reach $35B+ by 2030",
          "Audiobook listeners grew 25%+ year-over-year in recent years",
          "Authors who add audio versions typically see 10–30% incremental revenue on top of ebook/print sales",
          "With Echo3s, ROI is almost immediate — a $79 investment can generate hundreds or thousands in lifetime audiobook sales",
        ],
      },
      payment_methods:
        "Visa, Mastercard, American Express via Stripe. 14-day money-back guarantee on annual plans. Upgrade, downgrade, or cancel anytime.",
      cta: "See full pricing at https://echo3s.io/pricing — start free with 5,000 credits, upgrade when ready.",
    };
  • src/content.ts:983-989 (registration)
    The tool definition registration for 'get_pricing' in the TOOL_DEFS array. It maps the tool name 'get_pricing' to the 'pricing' data object via the content() function.
    {
      name: "get_pricing",
      description:
        "Get Echo3s pricing plans, credit system, cost breakdowns, and payment details",
      inputSchema: { type: "object", properties: {}, required: [] },
      content: () => pricing,
    },
  • src/index.ts:13-22 (registration)
    Registration of all tools (including get_pricing) with the McpServer in the stdio entry point. Each tool from TOOL_DEFS is registered via server.tool().
    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),
          },
        ],
      }));
    }
  • src/worker.ts:22-26 (registration)
    Registration of all tools (including get_pricing) into the TOOLS map in the Cloudflare Worker entry point. The defToWorkerTool function wraps the content() call into a handler.
    const TOOLS: Record<string, WorkerToolDef> = {};
    
    for (const def of TOOL_DEFS) {
      TOOLS[def.name] = defToWorkerTool(def);
    }
  • The input schema for get_pricing — an empty object schema meaning the tool takes no arguments.
    inputSchema: { type: "object", properties: {}, required: [] },
    content: () => pricing,
Behavior3/5

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

With no annotations provided, the description carries the full burden. It describes the tool's purpose but does not disclose behavioral details such as idempotency, data freshness, or any access restrictions. The description is clear but could be enhanced with non-functional traits.

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, focused sentence that covers all relevant components of pricing without extraneous information. Every word contributes to understanding.

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

Completeness5/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, low complexity), the description is complete. It adequately covers all aspects of pricing information retrieval without needing additional details.

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 the schema coverage is 100%. According to guidelines, a baseline of 4 is appropriate since the description adds no semantic meaning beyond the schema, but the schema already fully defines the input.

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 specifies that the tool retrieves pricing plans, credit system, cost breakdowns, and payment details, using a specific verb ('get') and distinct resources. It effectively distinguishes itself from sibling tools like get_faq or get_technical_specs.

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 for obtaining pricing information, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or context. It is adequate but lacks explicit differentiation.

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