MCP server that provides extensible command palette workflow launching capabilities with hotkey-triggered actions
This server has a single tool 'execute_skill_action' with critical definition gaps. The tool has a generic description (58 chars) that does not explain what it does, when to use it, or what it returns. No input schema is visible in the source code, the tool appears to be declared only in a JSON status message with no formal registration. The client.py and example_usage.py files show mock implementations, not actual tool definitions. No parameter descriptions, types, or constraints are present. No output schema is documented. The server does not implement the MCP protocol correctly, it only prints a JSON status message and exits, with no STDIO message loop or proper request/response handling.
Execute a skill action through the extensible command palette workflow launcher
No input schema visible for execute_skill_action. Tool definition appears inferred from JSON status message only, not formally registered with MCP protocol.
Tool description is generic and under 20 characters after 'Execute a skill action through the extensible command palette workflow launcher' (58 chars total). Does not explain WHAT the tool does, WHEN to use it, or WHAT it returns.
No parameters documented. Tool name 'execute_skill_action' is vague, does not start with a clear action verb and does not indicate what 'skill action' means or what parameters it accepts.
No output schema documented. LLM cannot infer what fields the tool returns or how to chain results to downstream tools.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 16 | 2026-07-28+ | v2 |
Server does not implement MCP protocol. mcp_server.py prints a single JSON message and exits, no STDIO message loop, no request/response handling, no tool invocation support.