Critical failures across all dimensions. The single tool 'command_runStudioCommand' has an empty input schema (no properties, no descriptions), a minimal description ('Runs a studio command action'), and no documented output schema. The tool name violates verb_noun conventions (uses camelCase with 'run' + 'Studio' + 'Command', unclear what action it performs). No parameter documentation exists. This server provides almost no guidance to an LLM about when or how to invoke the tool, what inputs it accepts, or what it returns. The codebase shows a TypeScript/Electron desktop app with Python backend, but the MCP tool definition is severely underdeveloped.

• Expand tool description to 100 - 200 characters explaining: (1) what studio command is executed, (2) when to call this tool, (3) what parameters it accepts, (4) what it returns. Example: 'Executes a studio command action (e.g., render, export, transform). Accepts a command name and optional parameters. Returns success status and result data.'
• Add explicit input parameters to the schema. Replace empty properties with at least: command (string, required, enum of valid commands), parameters (object, optional, command-specific args). Document each parameter.
• Document the output schema. Specify return fields: success (boolean), result (object or string), error (string if failed). Include example output.
• Rename tool to follow verb_noun convention. If it executes studio commands, use 'execute_studio_command' or 'run_command'. If it performs a specific action (render, export), name it accordingly.
• Add error handling guidance. For a WRITE tool, describe what can go wrong (invalid command, missing parameters, execution failure) and how the LLM should recover (retry, ask user, suggest alternatives).