Skip to content

Accept any JSON value as structuredContent in vMCP #5762

Description

@JAORMX

Part of #5743 (Workstream C: 2026-07-28 stateless readiness).

Work

vMCP rejects tool results whose structuredContent is not a JSON object — arrays/primitives are "not supported" (pkg/vmcp/client/client.go:926). The 2026-07-28 revision (SEP-2106) explicitly allows structuredContent to be any JSON value, with schemas as full JSON Schema 2020-12.

  • Accept any JSON value for structuredContent in vMCP's client/conversion path and forward it faithfully.
  • Check the composer's output validation/construction for the same object-only assumption.

Small, self-contained. Can land before the rest of Workstream C.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageIssue needs initial triage by a maintainer

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions