We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sparesparrow/mcp-prompts'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
voice-command-design-principles.json•4.8 kB
{
"id": "voice-command-design-principles",
"name": "voice-command-design-principles",
"description": "Design principles for effective voice command interfaces in MIA",
"content": "# Voice Command Design Principles for MIA\n\n## Device Type: {{deviceType}}\n## User Context: {{userContext}}\n## Focus Areas: {{focusAreas}}\n\n## Core Design Principles\n\n### Clarity and Precision\n- **Commands should be unambiguous**: Avoid homophones and context-dependent meanings\n- **Use natural language patterns**: Match how users actually speak\n- **Provide clear feedback**: Always confirm command interpretation\n\n### Context Awareness\n- **Location matters**: Home vs. office vs. vehicle commands differ\n- **Time sensitivity**: Morning routines vs. evening shutdowns\n- **User state**: Work mode vs. personal mode vs. family mode\n\n### Error Handling\n- **Graceful degradation**: If uncertain, ask for clarification\n- **Fallback options**: Provide alternative ways to accomplish tasks\n- **Learning from mistakes**: Remember and adapt to misinterpretations\n\n## Device-Specific Considerations\n\n### Mobile (Android)\n- **Privacy first**: Process locally when possible\n- **Battery conscious**: Optimize for power efficiency\n- **UI integration**: Seamlessly work with Android ecosystem\n\n### Raspberry Pi (Home Automation)\n- **Always-on capability**: Handle continuous listening responsibly\n- **Network reliability**: Work offline when internet unavailable\n- **Hardware integration**: Coordinate with GPIO and sensors\n\n### Multi-Device Coordination\n- **State synchronization**: Commands should work across devices\n- **Handover capability**: Start on phone, continue on Pi\n- **Conflict resolution**: Handle simultaneous commands intelligently\n\n## User Context Patterns\n\n### Developer Context\n- **Technical commands**: \"run tests\", \"deploy to staging\", \"check logs\"\n- **Precise terminology**: Use exact technical terms they expect\n- **Quick actions**: Fast, efficient command execution\n\n### Homeowner Context\n- **Natural language**: \"turn on the living room lights\"\n- **Conversational**: \"what's the temperature in the kitchen?\"\n- **Routine-based**: \"good morning routine\", \"bedtime setup\"\n\n## Focus Area Optimization\n\n### {{focusAreas}}\nBased on detected usage patterns:\n\n**If frequent commands are technical:**\n- Prioritize precision and speed\n- Use technical vocabulary\n- Minimize confirmation dialogs\n\n**If frequent commands are routine:**\n- Optimize for natural speech patterns\n- Add personality and conversational elements\n- Provide rich contextual feedback\n\n**If frequent commands involve multiple devices:**\n- Implement seamless handovers\n- Provide unified status across devices\n- Handle device-specific capabilities gracefully\n\n## Command Categories to Design\n\n### Action Commands\n- **Direct actions**: \"turn on/off\", \"set temperature\", \"play music\"\n- **Complex actions**: \"start workout routine\", \"prepare dinner\"\n- **Conditional actions**: \"if it's dark, turn on lights\"\n\n### Information Commands\n- **Status queries**: \"what's the temperature?\", \"is the door locked?\"\n- **Context queries**: \"what's on my calendar?\", \"any new messages?\"\n- **Capability queries**: \"what can you do?\", \"show available devices\"\n\n### Control Commands\n- **Mode switching**: \"developer mode\", \"quiet mode\", \"party mode\"\n- **Settings**: \"increase volume\", \"change language\", \"update preferences\"\n- **Management**: \"retrain voice model\", \"update device list\"\n\n## Implementation Guidelines\n\n### Voice Recognition Optimization\n- Train on user's actual speech patterns\n- Handle accents and speech impediments gracefully\n- Provide clear pronunciation guides for new commands\n\n### Response Design\n- Use consistent voice and personality\n- Provide appropriate detail level (terse vs. verbose)\n- Handle errors with helpful suggestions, not just failures\n\n### Privacy and Security\n- Never store sensitive voice data without explicit consent\n- Provide clear privacy controls and indicators\n- Implement secure command validation\n\n## Continuous Improvement\n\n### Learning Mechanisms\n- Track command success rates\n- Identify frequently misinterpreted commands\n- Adapt to changing user preferences\n- Update command vocabulary based on usage patterns\n\n### Feedback Integration\n- Allow users to correct misinterpretations\n- Learn from explicit feedback\n- Monitor satisfaction through usage patterns",
"isTemplate": true,
"variables": ["deviceType", "userContext", "focusAreas"],
"tags": ["mia", "voice-command", "design", "ux", "context-awareness"],
"category": "mia",
"version": 1,
"createdAt": "2025-01-01T00:00:00.000Z",
"updatedAt": "2025-01-01T00:00:00.000Z"
}