The server exposes only one tool: 'tool-catalog'. The tool name lacks a verb prefix (should be 'get_tool_catalog' or 'list_tools'). The description is present but minimal (47 chars, below the 50-200 char LLM-optimized range). No input schema is visible in the provided source code, the tool appears to be a simple read-only catalog fetch with no parameters. The Vue component calls `api<ToolCatalog>('tool-catalog')` but the actual MCP tool registration, input schema, and output schema are not shown. The server is primarily a Tauri desktop app with MCP as a secondary feature, not a production MCP server.

• Rename 'tool-catalog' to 'get_tool_catalog' to follow verb_noun convention and signal read-only intent to LLMs.
• Expand description to 80-150 characters: 'Retrieves the catalog of available tools with their metadata (name, description, group, presets, dependencies). Call this first to discover available tools before invoking them.'
• Document the output schema explicitly: ToolCatalog should include fields like tools (array of {name, description, group, requires}), groups (array), and required (array). Specify types and constraints for each field.
• Add error handling guidance: 'If the catalog fails to load, the connector may not be properly initialized. Check that the native service is running.'
• Provide the actual MCP tool registration code (from native/src or the MCP handler) showing the full schema, input parameters, and output structure.