Fix critical nested result structure in tools/call - remove incorrect result.result nesting
- tools/call was incorrectly nesting ScreenAsMcpTool result: result.result = [content: ...] - ScreenAsMcpTool already returns correct structure: result = [content: ...] - Creates nested result.result.result which breaks MCP spec and client parsing - Fix: Extract content directly from serviceResult.result instead of nesting - Resolves opencode client error: 'Typeundefined is not an object (evaluating result.content)' - Now result.content correctly accesses content array as expected by MCP clients
Showing
1 changed file
with
3 additions
and
2 deletions
| ... | @@ -265,9 +265,10 @@ | ... | @@ -265,9 +265,10 @@ |
| 265 | } | 265 | } |
| 266 | } | 266 | } |
| 267 | 267 | ||
| 268 | result.result = [ | 268 | // Extract content from ScreenAsMcpTool result, don't nest it |
| 269 | result = serviceResult?.result ?: [ | ||
| 269 | content: content, | 270 | content: content, |
| 270 | isError: serviceResult?.result?.isError ?: false | 271 | isError: false |
| 271 | ] | 272 | ] |
| 272 | return | 273 | return |
| 273 | } | 274 | } | ... | ... |
-
Please register or sign in to post a comment