issue: enums not present in Open API schema

[faevourite]

Check Existing Issues

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

mcpo Version

v0.0.17

Open WebUI Version (if applicable)

v0.6.26

Operating System

MacOS Sequoia, Docker

Browser (if applicable)

No response

Confirmation

• I have read and followed all instructions in README.md.
• I am using the latest version of both MCPO and Open WebUI.
• I have included the browser console logs.
• I have included the Docker container logs.
• I have listed steps to reproduce the bug in detail.

Expected Behavior

Enums listed in MCP field spec to show up in the converted OAI spec

Actual Behavior

No enum restrictions in OAI spec, just a plain string.

Steps to Reproduce

1. Use an MCP server that uses enums to constrain field values. I tried with Readwise MCP. Here's where it defines enums.
2. Check swagger json for the server and note that enums are missing.

Logs & Screenshots

Schema in MCP Inspector

No schema in MCPO

Additional Information

LLMs can get easily confused without enums info. For the Readwise MCP server, asking something simple like "search my readwise highlights for MCP" results in models guessing the field_name incorrectly (e.g. gemini tried "highlight_content").