feat: array support in custom tool OpenAPI input

[du00cs]

Self Checks

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

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I'm trying to use a custom tool of something like this:

openapi: 3.0.0
info:
  title: fake title
  description: API for creating recommended actions
  version: 1.0.0
servers:
  - url: https://abc.com
paths:
  /recommended_actions:
    post:
      summary: a summary
      description: a description
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                actions:
                  type: array
                  items: 
                    type: string
                  description: ...
                tts:
                  type: string
                  description: ...
      responses:
        '200':
          description: ... successfully

the actions field is declared to be array[string], but actually

and this will make the function call parameters to be string.

2. Additional context or comments

No response

3. Can you help us with this feature?

• I am interested in contributing to this feature.

[du00cs]

Maybe I can contribute to this feature, but actually I don't know how to.

[pigracing]

i have the same question, anybody who knows how to do?

[dosubot]

Hi, @du00cs. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• The issue involves the actions field in OpenAPI input being treated as a string instead of array[string].
• This affects function call parameters in custom tools.
• You expressed interest in contributing to a feature update but need guidance.
• Another user, @pigracing, has also encountered this issue and is seeking help.

Next Steps:

• Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here.
• If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!