fix(mcpserver): emit one TextContent block when a tool returns an empty list (issue #3305) - #3319
Open
gingeekrishna wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
All reported issues were addressed across 2 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
…ty list When a tool function returns an empty list or tuple, `func_metadata` was producing zero content blocks (an empty `CallToolResult.content`). The MCP spec requires at least one content item, so LLM clients that assume the list is non-empty would raise an index error or silently drop the result. Root cause: the branch that handled falsy sequences fell through to the normal `convert_result` path, which converts each element of the sequence into a `TextContent` block. An empty sequence produced nothing. Fix: detect `not result` before the element-wise conversion and return a single `TextContent` containing `[]` (the JSON serialisation of an empty list). Tuple return types are covered by the same branch. Signed-off-by: Radhakrishnan Pachyappan <gingeekrishna@gmail.com>
gingeekrishna
force-pushed
the
fix/3305-empty-list-zero-content-blocks
branch
from
August 17, 2026 04:53
39aef8c to
25a9532
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
listortuple,_convert_to_contentpreviously produced zero content blocks, making "no results" indistinguishable from "call produced nothing" for clients reading unstructured content.TextContentwhose text is the JSON-serialised empty collection ([]for bothlistandtuple).structuredContentis unaffected in all cases.Root cause
_convert_to_content(src/mcp/server/mcpserver/utilities/func_metadata.py:563) flattens a list by chaining the conversion of each item:With zero items there is nothing to concatenate, so the result is
[]. The same "empty" answer then behaves differently depending on return type:[]''[{...}, {...}]""''Fix
Tests added
Four new tests in
tests/server/mcpserver/test_func_metadata.py:test_empty_list_produces_one_text_content_block— core fix forlisttest_empty_tuple_produces_one_text_content_block— same guarantee fortupletest_non_empty_list_content_blocks_unchanged— non-empty path is byte-identicaltest_empty_list_structured_content_unaffected—structuredContentstill correctAll 46 tests in the file pass.
Test plan
uv run --frozen pytest tests/server/mcpserver/test_func_metadata.py— 46/46 pass[]now delivers one content block with text"[]"to the modelCloses #3305