Skip to main content
Glama
forgemeshlabs

Voice MCP

by forgemeshlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Generate Batch Voices

generate_batch_voices

Generate WAV audio for up to 20 text items in one call. Ideal for notifications, queues, scripted sequences, and multi-step agent workflows.

Instructions

Generate WAV audio for up to 20 text items in one paid call using standard voices. Best for queues, notifications, scripted sequences, content batches, and multi-step agent workflows. Costs $0.002 for up to 500 total chars or $0.005 for 501-2000 total chars.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesArray of text items; total text across all items must be <= 2000 chars
defaultsNoDefault standard voice and language

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.4
    • addedInput schema / properties / defaults / properties / lang / enum
      Added value: +[
+  "en",
+  "ko",
+  "ja",
+  "ar",
+  "bg",
+  "cs",
+  "da",
+  "de",
+  "el",
+  "es",
+  "et",
+  "fi",
+  "fr",
+  "hi",
+  "hr",
+  "hu",
+  "id",
+  "it",
+  "lt",
+  "lv",
+  "nl",
+  "pl",
+  "pt",
+  "ro",
+  "ru",
+  "sk",
+  "sl",
+  "sv",
+  "tr",
+  "uk",
+  "vi"
+]
    • addedInput schema / properties / defaults / properties / voice / enum
      Added value: +[
+  "M1",
+  "M2",
+  "M3",
+  "M4",
+  "M5",
+  "F1",
+  "F2",
+  "F3",
+  "F4",
+  "F5"
+]
    • changedInput schema / properties / items / description
      Previous value: -"Array of text items"New value: +"Array of text items; total text across all items must be <= 2000 chars"
    • addedInput schema / properties / items / items / properties / lang / enum
      Added value: +[
+  "en",
+  "ko",
+  "ja",
+  "ar",
+  "bg",
+  "cs",
+  "da",
+  "de",
+  "el",
+  "es",
+  "et",
+  "fi",
+  "fr",
+  "hi",
+  "hr",
+  "hu",
+  "id",
+  "it",
+  "lt",
+  "lv",
+  "nl",
+  "pl",
+  "pt",
+  "ro",
+  "ru",
+  "sk",
+  "sl",
+  "sv",
+  "tr",
+  "uk",
+  "vi"
+]
    • addedInput schema / properties / items / items / properties / text / maxLength
      Added value: +2000
    • addedInput schema / properties / items / items / properties / text / minLength
      Added value: +1
    • addedInput schema / properties / items / items / properties / voice / enum
      Added value: +[
+  "M1",
+  "M2",
+  "M3",
+  "M4",
+  "M5",
+  "F1",
+  "F2",
+  "F3",
+  "F4",
+  "F5"
+]
  2. Addedv0.1.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses cost and batch size but does not explain return format, synchronization behavior, or any side effects. Adds some value but lacks rich behavioral context.

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?

Two sentences: one functional overview and one usage advice. Front-loaded with key info. Efficient but could be slightly more structured with bullet points.

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 no output schema and 2 parameters, the description covers functionality, limits, cost, and use cases. It does not explain error handling or return format, but for a batch generation tool with clear schema, it is fairly complete.

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?

Schema description coverage is 100% (items and defaults have descriptions). The description only reiterates the batch limit and character limit already in schema, adding no further meaning.

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?

Description clearly states it generates WAV audio for up to 20 text items using standard voices, distinguishing it from siblings like generate_controlled_voice or generate_standard_voice. The verb 'generate', resource 'WAV audio', and scope 'batch' are specific.

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?

Explicitly lists use cases: queues, notifications, scripted sequences, etc. It does not directly state when not to use or name alternatives, but the context implies single items should use generate_standard_voice. Clear context without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools