Single tool 'get-table-info' has critical gaps. Description is in Spanish and lacks English clarity for LLM selection. Input schema exists (clientId: string) but parameter description is missing entirely, violates pattern:tool-description. No output schema documented. Error handling returns unstructured text responses instead of actionable recovery guidance. Tool name is verb-noun compliant but parameter naming is ambiguous ('clientId' suggests a user/client lookup, but actually queries a database table by ID). No pagination, no result limits, no structured output. STDIO transport caps protocol readiness at 50.

• Add English description to 'get-table-info': 'Retrieve a single database record by ID from the configured PostgreSQL table. Returns the full row as structured JSON. Requires a valid ID that exists in the table.'
• Add description to 'clientId' parameter: 'The unique identifier (primary key) of the record to retrieve. Must be a non-empty string matching an existing row ID in the table.'
• Document output schema explicitly: 'Returns an object with all columns from the matched row, or an error message if the ID is not found. Example: {id: string, name: string, email: string, ...}'
• Replace error handling with actionable recovery: Instead of 'Error al obtener información...', return structured error: {type: 'not_found', message: 'No record found with ID: ' + clientId, suggestion: 'Verify the ID is correct and exists in the table.'}
• Use parameterized queries for table name or validate against a whitelist: const allowedTables = ['clients', 'users']; if (!allowedTables.includes(tableName)) throw new Error('Invalid table');