This server has severe definition quality gaps. Only 2 tools are defined, both with minimal descriptions (under 50 chars). The executeTool schema is present but parameters lack descriptions, the 'parameters' field is documented only as 'Parameter name and value pairs for the tool', which is too vague. No output schemas are documented. Error handling is minimal (generic RuntimeException). The tool definitions appear to be meta-tools (listTools, executeTool) rather than domain-specific tools, which is unusual for an MCP server. No tool annotations (readOnlyHint, destructiveHint) despite executeTool being a WRITE operation.

• Expand tool descriptions to 100 - 200 characters. For listTools: 'Discovers and returns all available MCP tools registered in this Spring Boot application, including their names, descriptions, and parameter schemas. Call this first to see what tools are available.' For executeTool: 'Executes a registered MCP tool by name with the provided parameters. Returns the tool's result or an error if the tool is not found or execution fails. This is a write operation, use with caution.'
• Add descriptions to every parameter. For executeTool.parameters, replace the generic description with: 'A JSON object mapping parameter names to values. The structure depends on the target tool's schema. Example: {"user_id": "123", "status": "active"}. Validate against the tool's schema before calling.'
• Document output schemas for both tools. listTools should return: {"tools": [{"name": string, "description": string, "parameters": object}]}. executeTool should return: {"result": any, "success": boolean, "error": string (optional)}.
• Add tool annotations. Mark executeTool with destructiveHint=true (or false if it's read-only depending on the invoked tool) and idempotentHint=false (since reflection invocation may have side effects). Consider splitting into separate read and write tools.
• Improve error messages. Instead of 'Tool not found: X', return 'Tool "X" not found. Available tools: [list]. Did you mean one of these?' Instead of 'Error executing tool: X', return 'Tool "X" failed: [specific error]. Check parameters against the tool's schema and retry.'

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

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