Skip to content

feat: handle non-string returns from getmcptool#2668

Merged
neelneelneel merged 2 commits intodevfrom
runmcptool-return
Feb 10, 2026
Merged

feat: handle non-string returns from getmcptool#2668
neelneelneel merged 2 commits intodevfrom
runmcptool-return

Conversation

@tevanburen
Copy link
Copy Markdown
Contributor

@tevanburen tevanburen commented Feb 9, 2026

Description

We're updating RunMCPTool to return outputs of multiple types. This PR allows the SDK and Playground to handle these new returns
Goes with SEMOSS/Semoss#2030

Changes Made

Handle unknown return types

  • In the default tool UI
  • When auto-executing
  • When using actions.runMCPTool in the SDK

How to Test

  1. Have a tool that returns a non-string (for example, a map)
  2. Set it up to not auto-execute, and not have a custom UI. Verify that it still works
  3. Set it up to not auto-execute, and have a custom UI that calls actions.runMCPTool. Verify it still works
  4. Set it up to auto-execute. Verify it still works

@tevanburen tevanburen self-assigned this Feb 9, 2026
@tevanburen tevanburen linked an issue Feb 9, 2026 that may be closed by this pull request
@tevanburen tevanburen marked this pull request as ready for review February 9, 2026 19:17
@tevanburen tevanburen requested a review from a team as a code owner February 9, 2026 19:18
@neelneelneel neelneelneel merged commit 597f204 into dev Feb 10, 2026
3 checks passed
@neelneelneel neelneelneel deleted the runmcptool-return branch February 10, 2026 21:34
@github-actions
Copy link
Copy Markdown

@CodiumAI-Agent /update_changelog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RunMCPTool is returning bad JSON

2 participants