The issue you're encountering with testing the root endpoint in a custom tool without an operationId is likely related to the tool name validation in Dify. The error message "invalid tool name" suggests that the tool name might not be adhering to Dify's naming conventions. Dify requires tool names to only contain numbers, letters, and underscores ^[1].

To resolve this issue, ensure that the tool name in your Swagger schema or in the Dify interface follows these guidelines. If the operationId is missing, Dify automatically generates a tool_name, which must also comply with these naming rules. You might want to explicitly set an operationId in your Swagger schema to control the tool name and ensure it meets the requirements.

To continue talking to Dosu, mention @dosu.

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}