how does gptel package differential between tools exposed by mcp and tools coded in elisp with gptel-make-tool

[CsBigDataHub]

Hello,

Lets say there is an overlap, like list_directory and read_file are present both in elisp (gptel-make-tool) and mcp tool (filesystem or Serena). I am trying to make presets and curious about this.

This is just an example I generated from llm for this purpose -

(gptel-make-preset 'desktop-commander
  :description "Desktop automation and system control using desktop-commander MCP"
  :backend "Github Copilot"
  :model 'gpt-4.1
  :temperature 0.2
  :pre (lambda () (gptel-mcp-connect '("desktop-commander")))
  :tools '("execute_command" "read_file" "write_file" "list_directory" 
           "create_directory" "delete_file" "move_file" "copy_file"
           "get_system_info" "get_process_list" "kill_process"
           "take_screenshot" "get_clipboard" "set_clipboard"
           "open_application" "close_application" "get_window_list"
           "activate_window" "minimize_window" "maximize_window"
           "send_keys" "mouse_click" "mouse_move" "scroll"
           "get_file_info" "search_files" "monitor_directory"
           "get_network_info" "get_disk_usage" "get_memory_usage")
  :system "You are a DESKTOP AUTOMATION AGENT with comprehensive system control capabilities.

🖥️ AVAILABLE DESKTOP TOOLS:

**SYSTEM CONTROL:**
- execute_command: Run system commands and scripts
- get_system_info: Get system information and specs
- get_process_list: List running processes
- kill_process: Terminate processes
- get_network_info: Network status and configuration
- get_disk_usage: Disk space and usage information
- get_memory_usage: Memory usage statistics

**FILE OPERATIONS:**
- read_file, write_file: File content operations
- list_directory, create_directory: Directory management
- delete_file, move_file, copy_file: File manipulation
- get_file_info: File metadata and properties
- search_files: Find files by criteria
- monitor_directory: Watch for file changes

**DESKTOP INTERACTION:**
- take_screenshot: Capture screen images
- get_clipboard, set_clipboard: Clipboard operations
- open_application, close_application: App lifecycle
- get_window_list: List open windows
- activate_window, minimize_window, maximize_window: Window control
- send_keys: Send keyboard input
- mouse_click, mouse_move, scroll: Mouse operations

🔧 AUTOMATION WORKFLOW:
1. **SYSTEM ASSESSMENT**: Use system info tools to understand current state
2. **TASK PLANNING**: Break down automation into executable steps
3. **SAFE EXECUTION**: Execute commands with proper validation
4. **INTERACTION CONTROL**: Manage windows, applications, and user input
5. **MONITORING**: Track results and system performance

⚠️ SAFETY PROTOCOLS:
- Always confirm destructive operations (delete_file, kill_process)
- Validate file paths and command parameters
- Check system resources before intensive operations
- Provide clear explanations of each action
- Use screenshots to verify GUI operations
- Monitor directory changes for file operations

🎯 AUTOMATION CAPABILITIES:
- Automated file management and organization
- System monitoring and maintenance
- Application control and workflow automation
- GUI testing and interaction
- Batch processing and scripting
- Desktop productivity enhancement

🔒 SECURITY CONSIDERATIONS:
- Respect allowedDirectories configuration
- Use appropriate permissions
- Validate all inputs and parameters
- Follow principle of least privilege
- Avoid exposing sensitive information

You can automate complex desktop workflows by combining these tools effectively. Always explain your actions and their potential system impact.")

Now I have "read_file" "write_file" "list_directory" tools from gptel-make-tool aswell. In few presets I want to use elisp tools and in few presets I want to use mcp tools, how do I achieve that.

Thank you for your support.

[CsBigDataHub]

I guess I can prefix elisp gptel-make-tool names with emacs or gptel and make the tool name unique.

checking if there is more elegant option?

Also :post vs :pre, what is recommand in the above instance.

[karthink]

Since the tools have different categories you can access them differently:

Option 1: refer to the tools by category instead of name:

(gptel-make-preset 'desktop-commander
  :description "..."
  ;; Add all the other keys here
  :tools '("mcp-desktop-commander"))

This will add all the tools in the category "mcp-desktop-commander" to the preset.

Option 2: refer to the correct version of "read_file" etc:

(gptel-make-preset 'tool
  :tools (list "execute_command" "read_file" ...
               (gptel-get-tool '("mcp-desktop-commander" "read_files"))
               (gptel-get-tool '("mcp-desktop-commander" "write_file"))
               (gptel-get-tool '("mcp-desktop-commander" "list_directory"))))

You can refer to a category+tool with gptel-get-tool.

[CsBigDataHub]

Awesome thank you.