AIGigLab MCP Server

synthesize_voice

Generate spoken audio from text using a specific ElevenLabs voice ID.

Instructions

Generate audio from text using ElevenLabs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>",
      "voiceId": "<voiceId>"
    },
    "name": "synthesize_voice"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	The text content to speak.
`voiceId`	Yes	The ID of the voice to use (use list_voices to find IDs).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Jul 15, 2026

TDQS

C2.7/5.0

Behavior1/5

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

No annotations are provided, and the description only states 'Generate audio from text using ElevenLabs.' It fails to disclose any behavioral traits such as return format, latency, authentication requirements, or rate limits, leaving the agent uninformed.

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 sentence with no wasted words, effectively conveying the core purpose.

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?

For a tool that generates audio output, the description omits critical context such as the format of the returned audio, whether it is synchronous, error handling, or prerequisites. This leaves the agent with incomplete information to use the tool correctly.

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 coverage is 100% with both parameters described. The description adds the context 'using ElevenLabs' but adds no further semantics beyond the schema. Baseline score of 3 is appropriate.

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 ('Generate audio from text') and the resource ('using ElevenLabs'), making the tool's purpose clear. It distinguishes from siblings like transcribe_audio and compose_music, but does not explicitly contrast with other audio generation 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 alternatives such as compose_music or create_voice_clone. The description provides no context for selecting this tool.

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