Skip to main content
Glama
balloonf

Windows TTS MCP Server

by balloonf

get_tts_status

Check the current status of the Text-to-Speech (TTS) service on the Windows TTS MCP Server to monitor its operational state and ensure functionality.

Instructions

현재 TTS 상태를 확인합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_tts_status' tool. It checks the number of active TTS processes using the global running_processes list and process_lock, returning a status message indicating if TTS is active or idle.
    @mcp.tool()
    def get_tts_status() -> str:
        """현재 TTS 상태를 확인합니다"""
        try:
            active_count = 0
            
            with process_lock:
                # 실행 중인 프로세스 확인
                for process in running_processes[:]:
                    if process.poll() is None:  # 아직 실행 중
                        active_count += 1
                    else:  # 완료된 프로세스는 목록에서 제거
                        running_processes.remove(process)
            
            if active_count > 0:
                return f"[ACTIVE] 현재 {active_count}개의 음성이 재생 중입니다"
            else:
                return "[IDLE] 현재 재생 중인 음성이 없습니다"
                
        except Exception as e:
            return f"[ERROR] 상태 확인 오류: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'checks' status, implying a read-only operation, but doesn't specify what 'status' includes (e.g., active/inactive, errors, performance metrics), whether it requires authentication, or if there are rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, clear sentence in Korean: '현재 TTS 상태를 확인합니다.' It is front-loaded with the core purpose, has zero wasted words, and is appropriately sized for a simple status-check tool. Every word earns its place.

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 the tool's low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on what 'status' entails or behavioral context. Without annotations or output schema, the description should ideally provide more completeness about the return value or usage context, but it's not entirely incomplete for such a simple 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?

The tool has 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, so it meets the baseline expectation. No additional value is required or provided 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 purpose: '현재 TTS 상태를 확인합니다' translates to 'Check current TTS status.' This is a specific verb ('check') + resource ('TTS status') combination. However, it doesn't explicitly differentiate from sibling tools like 'test_tts' or 'stop_speech,' which prevents a perfect score.

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. With siblings like 'test_ts' (likely for testing) and 'stop_speech' (for stopping), there's no indication of when this status check is appropriate versus those actions. No explicit when/when-not or alternative recommendations are given.

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