dify publishes the workflow as a tool. After passing the parameters, it prompts: tool parameter url not found in tool config

[mxyd]

Self Checks

• [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
• [x] I have searched for existing issues search for existing issues, including closed ones.
• [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• [x] Please do not modify this template :) and fill in all the required fields.

Dify version

1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

dify publishes the workflow as a tool. After passing the parameters, it prompts: tool parameter url not found in tool config

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot[bot]]

I couldn't find any specific threads addressing the "tool parameter url not found in tool config" error. However, there is a similar closed issue regarding tool configuration errors. The suggested solution was to ensure that tools are properly configured and enabled in the agent's setup, and to adjust tool settings in the configuration interface to ensure they are active and correctly set up for use with the "FunctionCalling" strategy ^[1].

For your specific issue, it seems like the tool configuration might be missing the definition for the "url" parameter. Here are some steps you can take to troubleshoot and resolve this:

1. Check Tool Configuration: Ensure that the "url" parameter is correctly defined in the tool's configuration. Verify that the parameter name matches exactly with what is expected in the tool's setup.

2. Parameter Definition: Make sure the parameter is defined with the correct type and label. The type should be string, and it should be marked as required if necessary ^[2].

3. Configuration Interface: Double-check the configuration interface to ensure that all required fields are filled out correctly, including the identity and parameters sections ^[2].

4. Docker Setup: Since you are using a self-hosted Docker setup, ensure that any configuration changes are applied correctly. Use 'http://host.docker.internal' for connections to address network connectivity issues ^[3].

If these steps do not resolve the issue, consider reviewing the tool's YAML configuration file to ensure all necessary parameters are correctly specified.

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}

[HEI204]

same issue, did you solve this?

[k-kayashima]

me too.