I have searched the existing issues and discussions.
Problem Description
When adding a model with Tools (via mcpo) defaulted on in the model config as shown below, and 'Native' selected for function calling in advanced parameters, selecting that model in a new chat works perfectly.
However, when adding that model to an arena, the arena does not use the model's tools, and does not use Native function calling.
Steps followed:
Added an MCPO server to OpenWebUI, and ensured the tools work correctly when manually selected.
Created a new model in Workspace, with Function Calling Native, and enabled specific Tools to be on by default.
Opened the model in a New Chat, and queried it to confirm that the tools worked with no further configuration required.
Created a new Arena, and added the model from step 2.
Opened the arena in a New Chat, and queried it; but the tools did not work.
Troubleshooting determined that turning on Function Calling Native, and manually selecting Tools, resulted in the arena working for just the current chat; but a new chat requires these steps to be performed again.
Thank you for your great work!
Desired Solution you'd like
All defaults set in a model config, including Function Calling and selected Tools, should remain when using that model in an Arena.
If specific settings are set in the chat window of an Arena, this should override default settings; but if they have not been set the default settings from the Model should prevail.
Alternatives Considered
Training all Arena users to set function calling and tools per Conversation.
Additional Context
No response
Originally created by @ciejer on GitHub (May 26, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14326
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
When adding a model with Tools (via mcpo) defaulted on in the model config as shown below, and 'Native' selected for function calling in advanced parameters, selecting that model in a new chat works perfectly.
However, when adding that model to an arena, the arena does not use the model's tools, and does not use Native function calling.
Steps followed:
1. Added an MCPO server to OpenWebUI, and ensured the tools work correctly when manually selected.
2. Created a new model in Workspace, with Function Calling Native, and enabled specific Tools to be on by default.
3. Opened the model in a New Chat, and queried it to confirm that the tools worked with no further configuration required.
4. Created a new Arena, and added the model from step 2.
5. Opened the arena in a New Chat, and queried it; but the tools did not work.
6. Troubleshooting determined that turning on Function Calling Native, and manually selecting Tools, resulted in the arena working for just the current chat; but a new chat requires these steps to be performed again.
Thank you for your great work!
### Desired Solution you'd like
All defaults set in a model config, including Function Calling and selected Tools, should remain when using that model in an Arena.
If specific settings are set in the chat window of an Arena, this should override default settings; but if they have not been set the default settings from the Model should prevail.
### Alternatives Considered
Training all Arena users to set function calling and tools per Conversation.
### Additional Context
_No response_
Have you found any alternative options? I'm in a similar situation where I want to have an arena model use 2 workspace models that have some RAG and knowledge applied to them. I've found that when I add the 2 workspace ones that I modified the system prompt to those get ignored. It's like running the base models directly.
<!-- gh-comment-id:3225555964 -->
@ejames730 commented on GitHub (Aug 26, 2025):
Have you found any alternative options? I'm in a similar situation where I want to have an arena model use 2 workspace models that have some RAG and knowledge applied to them. I've found that when I add the 2 workspace ones that I modified the system prompt to those get ignored. It's like running the base models directly.
Nope - we're now using user tools and a filter function to achieve our a/b testing as the native arenas were not usable for our requirements.
<!-- gh-comment-id:3225921207 -->
@ciejer commented on GitHub (Aug 26, 2025):
Nope - we're now using user tools and a filter function to achieve our a/b testing as the native arenas were not usable for our requirements.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ciejer on GitHub (May 26, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14326
Check Existing Issues
Problem Description
When adding a model with Tools (via mcpo) defaulted on in the model config as shown below, and 'Native' selected for function calling in advanced parameters, selecting that model in a new chat works perfectly.
However, when adding that model to an arena, the arena does not use the model's tools, and does not use Native function calling.
Steps followed:
Thank you for your great work!
Desired Solution you'd like
All defaults set in a model config, including Function Calling and selected Tools, should remain when using that model in an Arena.
If specific settings are set in the chat window of an Arena, this should override default settings; but if they have not been set the default settings from the Model should prevail.
Alternatives Considered
Training all Arena users to set function calling and tools per Conversation.
Additional Context
No response
@ejames730 commented on GitHub (Aug 26, 2025):
Have you found any alternative options? I'm in a similar situation where I want to have an arena model use 2 workspace models that have some RAG and knowledge applied to them. I've found that when I add the 2 workspace ones that I modified the system prompt to those get ignored. It's like running the base models directly.
@ciejer commented on GitHub (Aug 26, 2025):
Nope - we're now using user tools and a filter function to achieve our a/b testing as the native arenas were not usable for our requirements.
@ejames730 commented on GitHub (Aug 27, 2025):
Thanks I'll look into that.
@tjbck commented on GitHub (Feb 22, 2026):
#20658