refactor: rename debug_issue tool to debug for brevity

- Rename debug_issue.py to debug.py
- Update tool name from 'debug_issue' to 'debug' throughout codebase
- Update all references in server.py, tests, and README
- Keep DebugIssueTool class name for backward compatibility
- All tests pass with the renamed tool

This makes the tool name shorter and more consistent with other
tool names like 'chat' and 'analyze'. The functionality remains
exactly the same.

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Fahad
2025-06-10 11:43:47 +04:00
parent 8c07ad1eb2
commit 67f18ef3c9
10 changed files with 32 additions and 32 deletions

View File

@@ -4,7 +4,7 @@ Tool implementations for Gemini MCP Server
from .analyze import AnalyzeTool
from .chat import ChatTool
from .debug_issue import DebugIssueTool
from .debug import DebugIssueTool
from .review_changes import ReviewChanges
from .review_code import ReviewCodeTool
from .think_deeper import ThinkDeeperTool

View File

@@ -16,7 +16,7 @@ from .models import ToolOutput
class DebugIssueRequest(ToolRequest):
"""Request model for debug_issue tool"""
"""Request model for debug tool"""
error_description: str = Field(..., description="Error message, symptoms, or issue description")
error_context: Optional[str] = Field(None, description="Stack trace, logs, or additional error context")
@@ -32,7 +32,7 @@ class DebugIssueTool(BaseTool):
"""Advanced debugging and root cause analysis tool"""
def get_name(self) -> str:
return "debug_issue"
return "debug"
def get_description(self) -> str:
return (