Skip to main content
Glama
balloonf

Windows TTS MCP Server

by balloonf

speak_fast

Converts text to speech at a high speed using Windows TTS functionality, enabling quick audio playback for efficient listening and content processing.

Instructions

텍스트를 빠른 속도로 읽어줍니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes

Implementation Reference

  • The speak_fast tool handler, registered via @mcp.tool(). Splits input text into chunks using split_text_for_tts, then spawns a daemon thread to speak each chunk quickly (rate=3) using powershell_tts.
    @mcp.tool()
    def speak_fast(text: str) -> str:
        """텍스트를 빠른 속도로 읽어줍니다"""
        try:
            # 텍스트 분할 (빠른 재생은 조금 더 짧게)
            text_chunks = split_text_for_tts(text, 400)
            total_chunks = len(text_chunks)
            
            def _speak_fast():
                for i, chunk in enumerate(text_chunks, 1):
                    safe_print(f"[FAST TTS] {i}/{total_chunks} 부분 재생 중: {chunk[:50]}...")
                    powershell_tts(chunk, rate=3, volume=100)  # 빠른 속도
                    if i < total_chunks:
                        time.sleep(0.3)  # 빠른 재생은 간격도 짧게
            
            thread = threading.Thread(target=_speak_fast, daemon=True)
            thread.start()
            
            if total_chunks > 1:
                return f"[FAST] 빠른 재생 시작 ({total_chunks}개 부분): '{text[:50]}...'"
            else:
                return f"[FAST] 빠른 재생 시작: '{text[:50]}...'"
            
        except Exception as e:
            return f"[ERROR] 빠른 재생 오류: {str(e)}"
  • Core helper function that executes TTS via PowerShell, using System.Speech.Synthesis.SpeechSynthesizer with configurable rate and volume. Manages processes and handles errors/timeouts.
    def powershell_tts(text: str, rate: int = 0, volume: int = 100) -> bool:
        """PowerShell을 사용한 TTS 실행"""
        process = None
        try:
            if platform.system() != "Windows":
                safe_print("[ERROR] Windows가 아닙니다")
                return False
            
            # 텍스트에서 작은따옴표 이스케이프 처리
            escaped_text = text.replace("'", "''")
            
            # PowerShell TTS 명령어
            cmd = [
                "powershell", "-Command",
                f"Add-Type -AssemblyName System.Speech; "
                f"$synth = New-Object System.Speech.Synthesis.SpeechSynthesizer; "
                f"$synth.Rate = {rate}; "
                f"$synth.Volume = {volume}; "
                f"$synth.Speak('{escaped_text}'); "
                f"$synth.Dispose()"
            ]
            
            # 프로세스 시작
            process = subprocess.Popen(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE, text=True)
            
            # 실행 중인 프로세스 목록에 추가
            with process_lock:
                running_processes.append(process)
            
            # 프로세스 완료 대기
            stdout, stderr = process.communicate(timeout=180)
            
            # 완료된 프로세스 목록에서 제거
            with process_lock:
                if process in running_processes:
                    running_processes.remove(process)
            
            if process.returncode == 0:
                safe_print(f"[SUCCESS] TTS 완료: {text[:30]}...")
                return True
            else:
                safe_print(f"[ERROR] TTS 오류: {stderr}")
                return False
                
        except subprocess.TimeoutExpired:
            safe_print("[WARNING] TTS 시간 초과")
            if process:
                process.kill()
                with process_lock:
                    if process in running_processes:
                        running_processes.remove(process)
            return False
        except Exception as e:
            safe_print(f"[ERROR] TTS 예외: {e}")
            if process:
                try:
                    process.kill()
                    with process_lock:
                        if process in running_processes:
                            running_processes.remove(process)
                except:
                    pass
            return False
  • Helper function to intelligently split long text into smaller chunks suitable for TTS, trying to preserve sentence boundaries using regex.
    def split_text_for_tts(text: str, max_length: int = 500) -> list:
        """텍스트를 TTS용으로 적절히 분할"""
        if len(text) <= max_length:
            return [text]
        
        # 문장 단위로 분할 시도
        import re
        sentences = re.split(r'[.!?。!?]\s*', text)
        
        chunks = []
        current_chunk = ""
        
        for sentence in sentences:
            # 문장이 너무 긴 경우 더 작게 분할
            if len(sentence) > max_length:
                # 쉼표나 기타 구두점으로 분할
                sub_parts = re.split(r'[,;:\s]\s*', sentence)
                for part in sub_parts:
                    if len(current_chunk + part) <= max_length:
                        current_chunk += part + " "
                    else:
                        if current_chunk.strip():
                            chunks.append(current_chunk.strip())
                        current_chunk = part + " "
            else:
                # 현재 청크에 문장을 추가할 수 있는지 확인
                if len(current_chunk + sentence) <= max_length:
                    current_chunk += sentence + ". "
                else:
                    if current_chunk.strip():
                        chunks.append(current_chunk.strip())
                    current_chunk = sentence + ". "
        
        # 마지막 청크 추가
        if current_chunk.strip():
            chunks.append(current_chunk.strip())
        
        return chunks
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'fast speed' which hints at performance, but doesn't cover critical aspects like whether this is a read-only operation, if it requires specific permissions, rate limits, or what happens to ongoing speech. For a TTS tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence in Korean that directly states the tool's function without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given the tool's moderate complexity (TTS operation with speed control), lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain return values, error conditions, or how 'fast speed' is implemented, leaving the agent with insufficient context for reliable use.

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 description implies the 'text' parameter by stating it reads text, adding meaning beyond the schema which has 0% description coverage. However, it doesn't provide details on text format, length limits, or language support. With only one parameter and low schema coverage, the description compensates adequately but not fully.

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 '텍스트를 빠른 속도로 읽어줍니다' (reads text at a fast speed) clearly states the tool's function with a specific verb ('reads') and resource ('text'), plus a behavioral modifier ('fast speed'). It distinguishes from siblings like 'speak_slow' and 'speak_quiet' by specifying speed, but doesn't fully differentiate from 'speak' which might imply normal speed.

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?

The description provides no guidance on when to use this tool versus alternatives like 'speak_slow', 'speak_quiet', or 'speak'. It mentions 'fast speed' but doesn't specify scenarios where fast speech is appropriate or when other tools should be preferred, leaving usage context entirely implicit.

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

Related 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/balloonf/widows_tts_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server