feat: Add get_tool_info function for better tool discoverability

[raifdmueller]

Summary

Implements Issue #24 - Add get_tool_info function for better tool discoverability and improved user experience.

What's Changed

New Handler Implementation

• Added GetToolInfoHandler in src/server/tool-handlers/get-tool-info.ts
  • Extends BaseToolHandler for consistency with existing patterns
  • Returns comprehensive JSON response with tool information
  • Includes current workflow state when available
  • Follows existing logging and error handling patterns

Integration Updates

• Updated tool registry in src/server/tool-handlers/index.ts

  • Import and register GetToolInfoHandler
  • Export handler class and types for external use

• Added MCP tool registration in src/server/server-config.ts

  • Register get_tool_info tool with proper schema
  • Set appropriate annotations (readOnly, idempotent)
  • Follow same pattern as other tool registrations

Features

The new get_tool_info() function provides:

• Complete tool inventory: Information about all 7 available tools (including itself)
• Workflow overview: All 7 available workflows with descriptions and phases
• Core concepts: Phase management, plan file tracking, conversation context
• Usage guidelines: Required patterns, phase transitions, context requirements
• Current state: Active workflow state when available (optional)

API Response Format

{
  "tool_name": "Responsible Vibe MCP - Development Workflow Management",
  "version": "1.0.0",
  "purpose": "Structured development workflows with guided phase transitions",
  "available_tools": [...],
  "available_workflows": [...],
  "core_concepts": {...},
  "usage_guidelines": {...},
  "workflow_states": {...}
}

Benefits

1. Improved Discoverability: Users can quickly understand all available functions
2. Better AI Integration: AI assistants can self-discover capabilities
3. Standardization: Follows established MCP patterns used by other servers
4. Reduced Learning Curve: Clear documentation of concepts and usage patterns
5. Debugging Support: Current status information helps troubleshoot issues

Implementation Quality

• ✅ Follows existing BaseToolHandler pattern
• ✅ Consistent with other tool handlers (list-workflows.ts, etc.)
• ✅ Proper error handling and logging
• ✅ No breaking changes to existing functionality
• ✅ Comprehensive response format for easy parsing

Testing

The implementation has been tested for:

• ✅ Proper handler registration in tool registry
• ✅ MCP server tool registration
• ✅ Response format consistency
• ✅ Integration with existing codebase

Ready for integration and further testing with MCP clients.

Related

Fixes #24