Bodega exposes 12 yum package management tools via TypeScript/MCP SDK. Critical gaps: NO visible input schemas in provided source code (mcp-server/src/tools/*.ts files not shown), descriptions are minimal (10-30 chars, well below 50-200 char baseline), and parameter documentation is absent. Tool names follow verb_noun pattern (yum_install, yum_remove) but lack LLM-optimized descriptions explaining WHEN to use each tool vs alternatives. No evidence of output schema documentation, error recovery guidance, or parameter constraints. The server.ts shows tool registration but actual schema definitions are not visible in the provided code sample.

• Add full JSON Schema definitions to each tool with type, description, enum, and minLength/maxLength constraints for all parameters. Example: { type: 'string', description: 'Package name to install (e.g., curl, vim). Use yum_search first if unsure.', minLength: 1, maxLength: 256 }.
• Expand tool descriptions to 80-150 characters. Include WHEN to use (e.g., 'Use yum_search to find packages by keyword before calling yum_install'), prerequisites, and risk level. Example: 'Install a package via yum. Call yum_search first if you don't know the exact package name. This modifies system state and can be undone with yum history undo.'
• Document output schemas for all tools. Specify returned fields, types, and pagination. Example for yum_search: { packages: [{ name: string, version: string, description: string, size: string }], total: number, limit: number }.
• Add error handling guidance to destructive tools. Example for yum_remove: 'If removal fails due to dependencies, call yum_info <package> to see dependents, or use yum history undo <id> to revert.'
• Implement parameter validation with actionable error messages. Instead of 'Invalid input', return 'Package name must be 1-256 alphanumeric characters. Got: "<value>"'. This enables LLM self-correction.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry