5ire is a desktop MCP client, not an MCP server providing tools to agents. The 8 'tools' listed are actually internal service functions for managing MCP server configurations and tool invocation, not tools that agents would call. Tool definitions lack proper descriptions, parameter validation, error guidance, and output schemas. Most tools have minimal documentation (under 50 chars) and incomplete schemas. The 'call' tool is particularly problematic: it exposes raw MCP tool invocation without safety rails, error recovery guidance, or output structure documentation. Schema quality is inconsistent, some tools have object-typed 'options' params with nested properties, but these lack type declarations and descriptions for nested fields. No tool provides enums, ranges, or format constraints. Error handling is absent from descriptions. The liveServers and liveActiveServers tools document behavior ('continuously pushes updates') but lack schema definitions for return types.

• Add return type schemas for all tools. At minimum: createServer should return {server_id: string, label: string, status: 'active'|'inactive'}. liveServers should return {servers: [{id, label, transport, endpoint, active}], total_count: number}.
• Declare 'transport' parameter in createServer as enum: type: 'string', enum: ['stdio', 'http'], description: 'Transport type, stdio for local processes, http for remote servers with URLs'.
• Add descriptions to all nested properties in 'options' objects. E.g., endpoint: {type: 'string', description: 'Remote HTTP server URL (required if transport=http, ignored if transport=stdio)'}.
• Add error guidance to each tool description. E.g., deleteServer: 'Permanently deletes the server configuration. This cannot be undone. Returns error if server is currently active, deactivate first.'
• Implement a confirmation flow for deleteServer. Add a separate tool 'confirm_delete_server' that takes a deletion token from deleteServer's dry-run response, or enhance deleteServer to accept a 'confirm_deletion: true' flag with prominent warnings in the description.
• Document the 'call' tool with explicit safety notes. Include: maximum execution time (e.g., 30s timeout), expected return structure, error recovery (retry logic, fallbacks), and limits on parameter size and result size.
• Replace free-form 'approvalPolicy' in updateServer with enum: ['none', 'user_approval', 'admin_approval'] to prevent invalid values.
• Add 'required' array to schemas. E.g., createServer should require at minimum ['transport'] and for HTTP servers also require ['endpoint']. updateServer should require at minimum ['id'].