github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.2k Packages Projects Releases 126 Wiki Activity

issue: Tools info not shown in UI #5492

New Issue
Closed
opened 2025-11-11 16:22:34 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-11 16:22:34 -06:00
Owner
Copy Link

Originally created by @m-ibm on GitHub (Jun 10, 2025).

Check Existing Issues

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

Installation Method

Docker

Open WebUI Version

v0.6.13

Ollama Version (if applicable)

v0.6.6

Operating System

RedHat, Windows 11, Ubuntu 20.04

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 a (MCP) tool server through the user settings the UI shows:

  1. The tools (and info about them) available from the tools server
  2. When a tool is called this is displayed in the UI
    2.1 The name of the tools is displayed
    2.2 Clicking a tool user can see parameters (latest version) and tool response
    2.3 The tools are properly quoted in the response

Actual Behavior

None of these is available through the admin-added tool server.
This means that I have to provide instructions to the users on how to each add the tools server if they want to get a proper experience.

I debated whether this is a feature request or a bug report, however, since all these are available for user-added tool servers I see this as a bug.

Steps to Reproduce

Just add a tools server via user settings then try the same via admin settings and see the huge difference in behavior.

Logs & Screenshots

N/A

Additional Information

No response

Originally created by @m-ibm on GitHub (Jun 10, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.13 ### Ollama Version (if applicable) v0.6.6 ### Operating System RedHat, Windows 11, Ubuntu 20.04 ### 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 a (MCP) tool server through the user settings the UI shows: 1. The tools (and info about them) available from the tools server 2. When a tool is called this is displayed in the UI 2.1 The name of the tools is displayed 2.2 Clicking a tool user can see parameters (latest version) and tool response 2.3 The tools are properly quoted in the response ### Actual Behavior None of these is available through the admin-added tool server. This means that I have to provide instructions to the users on how to *each* add the tools server if they want to get a proper experience. I debated whether this is a feature request or a bug report, however, since all these are available for user-added tool servers I see this as a bug. ### Steps to Reproduce Just add a tools server via user settings then try the same via admin settings and see the huge difference in behavior. ### Logs & Screenshots N/A ### Additional Information _No response_
GiteaMirror added the bug label 2025-11-11 16:22:34 -06:00
GiteaMirror commented 2025-11-11 16:22:35 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Jun 10, 2025):

Intended behaviour, information is not being displayed on purpose. However, we'd be open to PRs optionally addressing this feature request.

@tjbck commented on GitHub (Jun 10, 2025): Intended behaviour, information is not being displayed on purpose. However, we'd be open to PRs *optionally* addressing this feature request.
GiteaMirror commented 2025-11-11 16:22:35 -06:00
Author
Owner
Copy Link

@jasonpnnl commented on GitHub (Jun 20, 2025):

@tjbck Could you explain the thought behind this behavior and why admin added tool calls would not cite the tool call as part of the response?

@jasonpnnl commented on GitHub (Jun 20, 2025): @tjbck Could you explain the thought behind this behavior and why admin added tool calls would not cite the tool call as part of the response?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#5492
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?