Skip to main content
Glama
balloonf

Windows TTS MCP Server

by balloonf

kill_all_tts

Terminates all running text-to-speech processes in Windows, ensuring clean system performance and resolving conflicts with TTS functionality.

Instructions

모든 TTS 관련 프로세스를 강제 종료합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The kill_all_tts tool handler function that forcibly terminates all managed TTS processes, PowerShell instances, and speech-related processes.
    @mcp.tool()
    def kill_all_tts() -> str:
        """모든 TTS 관련 프로세스를 강제 종료합니다"""
        try:
            # 1. 관리 중인 프로세스 종료
            with process_lock:
                for process in running_processes[:]:
                    try:
                        process.kill()
                        running_processes.remove(process)
                    except:
                        pass
                running_processes.clear()
            
            # 2. 시스템의 모든 PowerShell TTS 프로세스 강제 종료
            try:
                subprocess.run([
                    "taskkill", "/F", "/IM", "powershell.exe"
                ], capture_output=True, timeout=10)
            except:
                pass
            
            # 3. Speech 관련 프로세스 정리
            try:
                subprocess.run([
                    "powershell", "-Command",
                    "Get-Process | Where-Object {$_.ProcessName -like '*speech*' -or $_.CommandLine -like '*Speech*'} | Stop-Process -Force"
                ], capture_output=True, timeout=5)
            except:
                pass
            
            return "[KILL] 모든 TTS 프로세스를 강제 종료했습니다"
            
        except Exception as e:
            return f"[ERROR] 강제 종료 오류: {str(e)}"
  • Registration of the kill_all_tts tool via the @mcp.tool() decorator.
    @mcp.tool()
  • Usage of kill_all_tts within the emergency_silence tool.
    kill_all_tts()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool performs '강제 종료' (force termination), which implies a destructive operation, but doesn't specify whether this is reversible, what side effects might occur, or what permissions are required. For a potentially destructive tool with zero annotation coverage, this is a significant gap.

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 that directly states the tool's purpose without any unnecessary words. It's appropriately sized for a simple tool and front-loads the essential information. Every word earns its place.

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 potentially destructive tool with no annotations and no output schema, the description is inadequate. It doesn't explain what '강제 종료' entails, whether there are confirmation steps, what happens to ongoing processes, or what the return value might be. Given the complexity implied by 'force termination' and the lack of structured documentation, more behavioral context is needed.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description doesn't need to explain any parameters, and it correctly doesn't attempt to do so. This meets the baseline expectation for a zero-parameter tool.

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 action ('강제 종료합니다' - force termination) and target ('모든 TTS 관련 프로세스' - all TTS-related processes). It uses specific verbs and identifies the resource being acted upon. However, it doesn't explicitly differentiate from sibling tools like 'stop_speech' or 'emergency_silence', which might have overlapping functionality.

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 'stop_speech' or 'emergency_silence'. There's no mention of prerequisites, appropriate contexts, or warnings about when not to use it. The agent must infer usage from the tool name and description alone.

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