QuickApps version
latest
What is the problem this feature will solve?
Let's say we have a public URL with PDF file (e.g. https://www.imf.org/-/media/files/publications/weo/2026/january/english/text.pdf).
The following use-cases should be supported:
- Some app (e.g. DIAL RAG) supports URL attachments -> agent should be able to send this file as URL attachment to the app.
- Some app does not support URL attachments, but supports in-DIAL attachments -> download this file to DIAL and send as regular attachment.
- MCP server supports URL as argument -> agent should be able to send this URL to the MCP server.
- MCP server supports in-DlAL attachments -> download this file to DIAL and send as regular attachment.
- MCP server supports base64 attachments -> download file and encode to base64.
What is the feature you are proposing to solve the problem?
- extend the
tool-call-file-parameter-formatting skill to support new use-cases
- extend tool args processing code to support new use-cases
- implement integration tests
What alternatives have you considered?
No response
QuickApps version
latest
What is the problem this feature will solve?
Let's say we have a public URL with PDF file (e.g. https://www.imf.org/-/media/files/publications/weo/2026/january/english/text.pdf).
The following use-cases should be supported:
What is the feature you are proposing to solve the problem?
tool-call-file-parameter-formattingskill to support new use-casesWhat alternatives have you considered?
No response