vocametrix

vocametrix_synthesize_speech

Synthesize speech from text with Azure neural voices, providing an audio URL and word-level timing data for voice analysis or pronunciation assessment.

Instructions

Synthesize speech from text using Azure neural text-to-speech. Returns an audio URL and word-level timing data. Supports all Azure Neural voice names for the requested locale.

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>"
    },
    "name": "vocametrix_synthesize_speech"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	Text to synthesize (max 1000 characters)
`speakerLocale`	No	BCP-47 locale code, e.g. "en-US", "fr-FR", "es-ES"	en-US
`voiceName`	No	Azure Neural voice name, e.g. "en-US-JennyNeural"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 10, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It adds behavioral context by noting the use of Azure neural TTS, return of timing data, and support for all voice names per locale. However, it lacks details on synchronous/asynchronous behavior, error handling, or rate limits.

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 extremely concise with only two sentences, yet it conveys the core function, output type, and a key feature (voice name support). No fluff or redundant information.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description provides the essential purpose and outputs but lacks important context such as error conditions, prerequisites, or differentiation from the sibling tool that also returns timing data. Adequate but incomplete.

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%, so the schema already explains each parameter. The description adds minimal extra value, only noting that all Azure Neural voice names are supported for the locale. Baseline 3 is appropriate as the description does not significantly enhance parameter understanding beyond the schema.

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 tool's function: 'Synthesize speech from text using Azure neural text-to-speech.' It also specifies outputs: audio URL and word-level timing data. However, it does not differentiate from the sibling tool 'vocametrix_synthesize_speech_with_timing,' which may cause confusion about their distinct purposes.

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 is provided on when to use this tool versus alternatives, such as the similar sibling or other synthesis tools. The description only states what the tool does, leaving the agent without contextual usage advice.

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

Deploy Server