Fix Tool Edit Screen: Field Mapping Consistency and Custom Tool Naming Implementation

[rakdutta]

Overview

This PR resolves issue #715 by implementing custom tool naming functionality and fixing field mapping inconsistencies in the tool edit screen. The changes improve the user experience by distinguishing between MCP and REST tool editing capabilities while maintaining backward compatibility.

---

Key Features

🔹 Custom Tool Naming

• New custom_name field: Allows users to set display names independent of original MCP server tool names
• Database migration: Safely transitions from original_name_slug → custom_name / custom_name_slug fields
• Auto-population: Defaults custom_name to original_name if not explicitly provided
• Slug generation: Automatically creates URL-safe custom_name_slug for internal routing

🔹 Enhanced Tool Edit Logic

MCP Tools (Read-only constraints):

• URL field is read-only (cannot modify MCP server endpoints)
• Headers, input schema, and auth fields are disabled
• Integration type cannot be changed from MCP → REST
• Prevents invalid configuration changes

REST Tools (Full editing):

• All fields remain editable with validation
• URLs, headers, schemas, and authentication are modifiable
• Integration type can be changed between REST variants

🔹 UI/UX Improvements

• Field validation for custom names using existing security patterns
• Clear visual feedback for read-only vs editable fields
• Alerts for invalid operations (e.g., REST → MCP conversion)
• Hidden name field maintains API compatibility while displaying customName to users

---

Technical Details

Database Changes

ALTER TABLE tools DROP COLUMN original_name_slug;
ALTER TABLE tools ADD COLUMN custom_name VARCHAR;
ALTER TABLE tools ADD COLUMN custom_name_slug VARCHAR;

API Schema Updates

# ToolUpdate now supports custom naming
class ToolUpdate(BaseModel):
    name: Optional[str] = Field(None, description="Unique name for the tool")
    custom_name: Optional[str] = Field(None, description="Custom name for the tool")
    # ... other fields

# ToolRead includes both custom and computed names
class ToolRead(BaseModel):
    custom_name: str
    custom_name_slug: str
    # ... other fields

Frontend Logic

• Tracks integration type changes to prevent invalid transitions
• Dynamically enables/disables fields based on tool type
• Provides immediate user feedback

---

Backward Compatibility

• Migration strategy: Existing tools auto-populate custom_name_slug from original_name_slug
• API compatibility: Extends functionality while keeping endpoints unchanged
• Form handling: Hidden fields ensure submissions work with existing backend logic

---

Testing

Verified functionality through both the UI and API endpoints.

[madhav165]

Works as expected.

1. Added tools with MCP server
2. Updated tool name from edit tool box
3. Tool shows with updated name in gateway and other clients like MCP Inspector and tool works.

GOOD TO MERGE.

@rakdutta Do we need to allow editing name in update_tool function in tool_service?

[crivetimihai]

Rebased and tested

[rakdutta]

@madhav165
Raised PR #805
to remove name update logic from tool_service.py