The function can not be selected when body includes an array data

[swingboat]

I am using M365 agents toolkit to develop a declarative agent. I write an OpenAPI file and define a post request, its body includes an array of string and other data. the following is its code snippet:

requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                JiraInstance:
                  type: string
                  description: jira instance URL (e.g., https://your-domain.atlassian.net)
                ProjectKey:
                  type: string
                  description: The key of the Jira project (e.g., PROJ)
                IssueSummary:
                  type: string
                  description: Summary of the Jira issue
                IssueDescription:
                  type: string
                  description: Detailed description of the Jira issue
                IssueType:
                  type: string
                  description: The type of Jira issue (e.g., Task, Bug)
                Comments:
                  type: array
                  items:
                    type: string
                    description: Comments to be added to the issue
                  description: Additional comments to be added to the issue
                  example: ["Initial comment", "Follow-up comment"]
                  default: []
              required:
                - ProjectKey
                - IssueSummary
                - IssueDescription
                - IssueType
                - Comments

when I test this agent, if I don't set comments, then this function can be called. If I set comments, such as ["test1", "test2"], then this function will not be called. why? I think it maybe a issue of Copilot agent.

Additionally, when the "Confirmation prompts" message appears, the value of "Comments" is correct(["test1", "test2"]), but this function still cannot be invoked. The following the information of Console:

ACTIONS
(√) Enabled action: Call Power Automate Flow to Create Jira Issue • version 1.0.0 • U_76233d65-6601-ccdd-b7cb-0881878fa257.menuPlugin
   (√) Matched functions: triggerPowerAutomateFlow
[2025-06-13T14:05:58.998Z] Debug: Stopping HubConnection.
82801.0b092ba0c065266ccb3a.chunk.js:1
[2025-06-13T14:05:58.999Z] Debug: HttpConnection.stopConnection(undefined) called while in state Disconnecting.
82801.0b092ba0c065266ccb3a.chunk.js:1
[2025-06-13T14:05:58.999Z] Information: Connection disconnected.
82801.0b092ba0c065266ccb3a.chunk.js:1
[2025-06-13T14:05:58.999Z] Debug: HubConnection.connectionClosed(undefined) called while in state Disconnecting.

[m365-agent-toolkit-assistant]

👋 Hi @swingboat,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 2 business days

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

From the information provided, your issue seems to be related to how the declarative agent handles arrays in the request body.

Potential Solutions:

1. Workaround Change:

   • Modify your schema to encapsulate the array within an object. Sometimes, the serialization/deserialization of arrays within request bodies can cause issues like yours. You could test the following change:

     Comments:
       type: object
       properties:
         items:
           type: array
           items:
             type: string
       description: Additional comments to be added to the issue
       example: { "items": ["Initial comment", "Follow-up comment"] }

2. Use Existing Known Issues:

   • This might relate to limitations or bugs in how arrays are handled. Consult your Teams Toolkit version and ensure it's updated.
   • Reference GitHub issues such as GitHub Issue #13650 where similar problems were discussed involving declarative agents and JSON handling.

Further Steps:

1. Debug and Logging:

   • If after the workaround the issue persists, ensure detailed debugging:
     • Environment: VS Code
     • Teams Toolkit Version
     • Exact Steps to Reproduce
     • Detailed Error Logs beyond the provided snippet

2. Validating the OpenAPI Specification:

   • Make sure your OpenAPI spec is fully compliant by using validators like Swagger Inspector or a similar tool.

By taking these steps, you should be able to determine the root cause and potentially resolve the issue or find a viable workaround. If further issues persist, consider raising them specifically on the Teams Toolkit GitHub repository.

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!