docs(sdk): describe structured MCP results - #771
Open
georgeglarson wants to merge 2 commits into
Open
Conversation
Co-authored-by: openhands <openhands@all-hands.dev>
1 task
georgeglarson
marked this pull request as ready for review
August 30, 2026 23:04
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
1 participant
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 of changes
Documents the two
MCPToolObservationfields added in OpenHands/software-agent-sdk#4775 (which closes software-agent-sdk#4776).The new paragraph in
sdk/arch/mcp.mdxrecords thatstructured_contentandresult_metakeep the MCP result'sstructuredContentand_metain the serialized observation for protocol-aware clients, that neither field is included in the tool-result content sent through the main agent loop, and that registered secrets in them are masked during conversation-backed execution (nested keys and values, secrets echoed as JSON numbers included). A field that cannot be masked safely, two keys colliding after masking for example, is dropped rather than returned unmasked.