Fix: Update MCP tool version.

[jbutlerdev]

Pull Request: Refactor MCP Command Line Parsing

Summary

This pull request refactors the command line argument parsing logic within tools/mcp.go. The changes focus on improving code readability and maintainability by leveraging the flag package more effectively and reducing code duplication. Specifically, it removes manual parsing of arguments and replaces it with structured flag definitions and a dedicated parsing process.

Motivation

The original implementation of command line argument parsing in tools/mcp.go was complex, verbose, and prone to errors. It relied on manually iterating through the os.Args slice and parsing parameters based on string comparisons. This approach made the code difficult to understand, modify, and extend. By migrating to the flag package, we gain several benefits:

• Simplified Syntax: The flag package provides a more concise and declarative way to define command-line arguments.
• Automatic Parsing: The flag package handles the parsing of command-line arguments, reducing the amount of manual code we need to write.
• Built-in Help: The flag package provides automatic generation of help messages, making the CLI tool more user-friendly.
• Reduced Code Duplication: We are moving away from custom parsing logic which appears in multiple places to a single, well-defined process.
• Improved Error Handling: The flag package provides standardized error handling for missing or invalid arguments.

These improvements will make the codebase more maintainable and easier to contribute to in the future.

Potential Impact or Breaking Changes

This change is not expected to have any breaking changes for users. The functionality of tools/mcp.go remains unchanged; it simply processes the command line arguments in a different way under the hood. The command-line arguments and expected behavior remain the same.

Testing Instructions

The changes made in this pull request primarily affect the internal implementation of command-line argument parsing, and do not alter the output or functionality of tools/mcp.go. To test these changes, one can:

1. Build the tool: go build ./tools/mcp.go
2. Run the tool using existing command line arguments that you would usually use. For example:
   ./mcp --operation create --parameter key=value
3. Verify that the tool behaves the same as it did before these changes, i.e. it processes the input arguments correctly and perform the expected actions.
4. Verify help message: ./mcp -h or ./mcp --help should now print usage instructions.
5. Verify invalid inputs are handled properly, such as providing invalid flags or required parameters are missing.

Closes #3