Skip to main content
Glama
balloonf

Windows TTS MCP Server

by balloonf

emergency_silence

Instantly stop all audio and mute system sounds to address urgent situations, using a command from the Windows TTS MCP Server.

Instructions

긴급 음소거 - 모든 오디오 중지 + 시스템 음소거

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'emergency_silence' tool. It kills all TTS processes, mutes the system volume using PowerShell SendKeys, and optionally uses nircmd if available.
    def emergency_silence() -> str:
        """긴급 음소거 - 모든 오디오 중지 + 시스템 음소거"""
        try:
            # 1. TTS 프로세스 모두 종료
            kill_all_tts()
            
            # 2. 시스템 음소거
            try:
                subprocess.run([
                    "powershell", "-Command",
                    "(New-Object -ComObject WScript.Shell).SendKeys([char]173)"  # 음소거 키
                ], capture_output=True, timeout=3)
            except:
                pass
            
            # 3. 대안: nircmd 사용 (설치되어 있다면)
            try:
                subprocess.run(["nircmd", "mutesysvolume", "1"], capture_output=True, timeout=3)
            except:
                pass
            
            return "[EMERGENCY] 긴급 음소거 실행 완료 (TTS 중지 + 시스템 음소거)"
            
        except Exception as e:
            return f"[ERROR] 긴급 음소거 오류: {str(e)}"
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does ('stop all audio + system mute') without disclosing behavioral traits such as whether this is reversible, requires permissions, affects other processes, or has side effects. For a potentially disruptive tool, 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 extremely concise (one short phrase) and front-loaded with the core action, making it easy to parse. Every word earns its place by conveying essential purpose without waste.

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 potential complexity (emergency system-level audio control) and lack of annotations or output schema, the description is incomplete. It fails to address critical context like reversibility, error handling, or confirmation requirements, which are essential for safe agent invocation.

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 no parameter documentation is needed. The description appropriately omits parameter details, earning a baseline score of 4 for not adding unnecessary information beyond 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 the tool's purpose with specific verbs ('긴급 음소거' translates to 'emergency silence') and resources ('모든 오디오 중지' means 'stop all audio' and '시스템 음소거' means 'system mute'). It distinguishes from siblings like 'stop_speech' by implying broader system-level action beyond just speech.

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 'kill_all_tts'. It lacks explicit context, prerequisites, or exclusions, leaving the agent to infer usage from the 'emergency' label without clear operational boundaries.

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