A
licenseA
qualityD
maintenanceProvides high-quality text-to-speech synthesis with 10 natural voices, emotion control, and dynamic pacing for professional applications requiring expressive speech output.
5
2
MIT
tts
Server Details
Hosted pay-per-use TTS: 54 neural voices, 9 languages incl. Brazilian Portuguese. $10 free credits.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- fasuizu-br/brainiall-tts-mcp
- GitHub Stars
- 0
- Server Listing
- brainiall-tts-mcp
Available Tools
3 toolscheck_tts_serviceCheck TTS ServiceARead-onlyIdempotentInspect
Check health status of the TTS API service.
Returns: dict with keys: - status (str): 'healthy' or error state
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false. The description adds disclosure of the return format (dict with status key), which is beyond annotations. No contradictions.
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?
Two lines for the return description, no extraneous text. Every sentence is meaningful and focused.
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 input schema and no output schema, but rich annotations, the description adequately describes the return format. However, it lacks detail on potential error states or interpretation beyond 'healthy' or error.
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?
Zero parameters, so the input schema covers everything. The description adds no extra parameter info, but none is needed. Baseline 4 for no-parameter tools.
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 'Check health status of the TTS API service', with specific verb ('check') and resource ('health status of TTS API service'). It distinguishes from sibling tools (list_voices, synthesize_speech) which do different tasks.
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?
No explicit guidance on when or when not to use this tool versus alternatives. Usage is implied for health checking, but no exclusions or alternative recommendations are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_voicesList VoicesARead-onlyIdempotentInspect
List available TTS voices with metadata.
54 neural voices across 9 languages. Each voice has an ID (used in synthesize_speech), display name, gender, accent and quality grade.
Args: language: Optional language filter (e.g. 'pt-br', 'en-us').
Returns: dict with keys: - voices (list): Each with id, name, gender, accent, lang, grade - count (int): Number of voices returned
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| language | No | Filter by language code (e.g. 'pt-br', 'en-us', 'ja'); omit for all 54 voices |
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by detailing the number of voices (54), languages (9), and return structure (id, name, gender, accent, lang, grade). No contradictions.
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?
Very concise: one-line purpose, bulleted args and returns. No fluff; every sentence adds value. Front-loaded with core verb and resource.
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 low complexity (1 optional param, no output schema), the description fully covers purpose, parameter usage, return format, and relation to siblings. No gaps.
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?
Schema coverage is 100% (1 parameter with description). The description adds real-world context: 'e.g. 'pt-br', 'en-us'' and default behavior ('omit for all 54 voices'), enriching the schema.
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 'List available TTS voices with metadata' and provides specifics (54 voices, 9 languages). It distinguishes itself from siblings: 'check_tts_service' (presumably service health) and 'synthesize_speech' (which uses a voice ID).
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 mentions optional language filter and notes the voice ID is used in 'synthesize_speech', guiding usage. However, it doesn't explicitly state when not to use this tool versus siblings, though the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
synthesize_speechSynthesize SpeechARead-onlyIdempotentInspect
Convert text to natural-sounding speech.
Returns WAV audio (16-bit PCM, 24 kHz mono) synthesized with neural voices. 54 voices across 9 languages -- including 3 native Brazilian Portuguese voices (pf_dora, pm_alex, pm_santa). Usage is metered per character.
Args: text: Text to convert to speech (max 5000 characters per request). language: Language code; selects the default voice when no voice is given. voice: Explicit voice ID (see list_voices). Overrides language. speed: Speech speed multiplier, 0.5-2.0. output_format: 'audio' for playable MCP audio content, 'base64_json' for a JSON object with the base64-encoded WAV and metadata.
Returns: MCP audio content (audio/wav), or when output_format='base64_json' a dict with keys: - audio_base64 (str): Base64-encoded WAV bytes - mime_type (str): 'audio/wav' - voice (str): Voice used - characters (int): Characters billed - estimated_cost_usd (float): Estimated cost of this request
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Text to convert to speech (1-5000 characters per request) | |
| speed | No | Speech speed multiplier (0.5 = half speed, 2.0 = double speed) | |
| voice | No | Voice ID (e.g. 'pf_dora', 'pm_alex', 'af_heart', 'bm_george'). Overrides 'language'. Use list_voices for the full catalog. | |
| language | No | Language code: 'pt' (Brazilian Portuguese, default), 'en', 'en-gb', 'es', 'fr', 'it', 'hi', 'ja', 'zh'. Used to pick a default voice when 'voice' is omitted. | pt |
| output_format | No | 'audio' (default) returns playable MCP audio content; 'base64_json' returns JSON with the base64-encoded WAV plus metadata | audio |
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent behavior. Description adds useful context: returns WAV format, neural voices, metered per character, character limit. No contradiction with annotations.
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?
Very concise: intro sentence, two lines of key details, then well-organized Args and Returns sections. No superfluous content.
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?
Covers all aspects: input constraints (character limit), output formats with full return structure for base64_json, examples of voices, and cost indication. No missing information for a typical TTS tool.
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?
Schema coverage is 100%, so description adds value by providing examples (voice IDs, language codes) and clarifying output_format options. Does more than just repeat schema.
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 converts text to speech, specifies the output format (WAV, 16-bit PCM, 24 kHz mono), and distinguishes from siblings like list_voices (lists voices) and check_tts_service (checks service).
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?
Provides guidance on character limit, metered usage, and voice/language selection, but does not explicitly contrast with sibling tools or state when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
3 tool updates
- First observed
check_tts_service - First observed
list_voices - First observed
synthesize_speech
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Hosted speech-to-text + speech emotion/tone analysis for agents. No install; trial keys built in.
Pronunciation scoring, speech-to-text, and text-to-speech for language learning
Transcribe audio & video to text for AI agents: 100+ languages, speaker labels, webhooks.
Generate images, video & speech with Nano Banana, Veo, Omni and Gemini TTS. Pay as you go.
Related MCP Servers
- FlicenseAqualityCmaintenanceConverts text or transcripts into MP3 audio using Microsoft Edge's free neural voices. Provides text-to-speech and voice listing tools with no API key required.2-
- AlicenseAqualityAmaintenanceGive your AI agent a voice with x402 pay-per-call speech synthesis, offering 20 voices, 10 personas, 31 languages, and granular controls.46198MIT
- FlicenseNot gradedqualityBmaintenanceLocal multilingual TTS (24 languages incl. Ukrainian) with zero-shot voice cloning, voice design, and speech editing via HTTP API and MCP server.3-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.4/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: health check, listing available voices, and converting text to speech. No overlap or ambiguity.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (check_tts_service, list_voices, synthesize_speech).
Tool Count4/5
3 tools is minimal but appropriate for a TTS service, covering health monitoring, voice discovery, and speech synthesis. A slight expansion could include voice details, but current set is reasonable.
Completeness4/5
The tool surface covers the core operations: check service health, list voices, and synthesize speech. Minor gaps, such as the inability to retrieve a single voice's details without listing all, but overall adequate for the stated purpose.