Read aloud text in a cute mascot character voice. Supports Japanese and English text, automatically converting English words to katakana. Plays audio directly on Windows from WSL environments.
テキストをかわいいマスコットキャラクターのような声で読み上げます。 ユーザーにお知らせするときはこのキャラクターになりきって楽しませながら報告しましょう！
日本語のテキストを音声合成し、WSL環境では自動的にWindows側で再生されます。 英単語が含まれている場合は自動的にカタカナに変換されます。
Args: text: 読み上げたいテキスト（日本語・英語混在可能）
Returns: 成功時は"✓"、エラー時はエラーメッセージ
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Explica síntesis de voz, reproducción en WSL, conversión de inglés a katakana, y mensajes de retorno. Sin anotaciones, la descripción es suficiente.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Información concisa con estructura clara: propósito, cuándo usarlo, comportamiento, argumentos y retorno. Sin redundancias.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Cubre todos los aspectos necesarios para un tool simple: propósito, uso, parámetros, comportamiento y resultado.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
El parámetro 'text' se describe claramente en la sección Args: texto a leer, admite japonés e inglés. Añade valor más allá del esquema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Descripción clara: indica que lee texto en una voz de mascota linda, y distingue de herramientas hermanas (diccionarios).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Sugiere usarlo para notificar usuarios de forma divertida, pero no excluye alternativas ni menciona cuándo no usarlo.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kurasuai-Inc/voice-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server