[GH-ISSUE #16669] issue: Tools with duplicate names are removed silently #18005

New Issue

GiteaMirror · 2026-04-19T23:54:33-05:00

GiteaMirror commented

2026-04-19 23:54:33 -05:00

Originally created by @antondelgado123 on GitHub (Aug 16, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16669

Check Existing Issues

I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

latest dev branch (and all previous version)

Ollama Version (if applicable)

No response

Operating System

Ubuntu

Browser (if applicable)

No response

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

When adding 2 MCPs (via MCPO) with the same tool names, I expect the LLM to be able to call the duplicate tool on each server.

For example, we use the official Clikhouse MCP. We further have 2 Clickhouse instances (EU and US) which results in 2 MCP instances. I want to be able to say - "Compare the results of query X across instances"

Actual Behavior

The desired behaviour does not happen - the LLM only calls one of the 2 MCPs. We receive the following log line

                        log.warning(
                            f"Tool {function_name} already exists in another tools!"
                        )

Steps to Reproduce

This Issue is created to comply with the contributor guidelines. I will submit a PR to fix it shortly.
Steps to reproduce are

run any MCP twice (on different ports / URLs)
Add the 2 instances to OI (via MCPO)
Execute a chat with both MCPs
check in the logs of the MCPs if both are called.

Logs & Screenshots

N/A

Additional Information

No response

Originally created by @antondelgado123 on GitHub (Aug 16, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16669 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version latest dev branch (and all previous version) ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior When adding 2 MCPs (via MCPO) with the same tool names, I expect the LLM to be able to call the duplicate tool on each server. For example, we use the official Clikhouse MCP. We further have 2 Clickhouse instances (EU and US) which results in 2 MCP instances. I want to be able to say - "Compare the results of query X across instances" ### Actual Behavior The desired behaviour does not happen - the LLM only calls one of the 2 MCPs. We receive the following log line ``` log.warning( f"Tool {function_name} already exists in another tools!" ) ``` ### Steps to Reproduce This Issue is created to comply with the contributor guidelines. I will submit a PR to fix it shortly. Steps to reproduce are 1) run any MCP twice (on different ports / URLs) 2) Add the 2 instances to OI (via MCPO) 3) Execute a chat with both MCPs 4) check in the logs of the MCPs if both are called. ### Logs & Screenshots N/A ### Additional Information _No response_

GiteaMirror added the bug label 2026-04-19 23:54:33 -05:00

GiteaMirror closed this issue

2026-04-19 23:54:34 -05:00

GiteaMirror referenced this issue

2026-04-20 05:30:38 -05:00

[PR #18005] [CLOSED] Leo's work #24634

GiteaMirror referenced this issue

2026-04-25 12:40:08 -05:00

[PR #18005] [CLOSED] Leo's work #40264

GiteaMirror referenced this issue

2026-04-29 23:01:25 -05:00

[PR #18005] [CLOSED] Leo's work #47682