From 741449391c2545580fd94ab4e30c3f1816887ce6 Mon Sep 17 00:00:00 2001
From: evalstate <1936278+evalstate@users.noreply.github.com>
Date: Wed, 3 Jun 2026 00:47:34 +0100
Subject: [PATCH] Update structuredContent guidance for TextContent blocks

---
 docs/specification/draft/server/tools.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/specification/draft/server/tools.mdx b/docs/specification/draft/server/tools.mdx
index 8d0b5e87f..079e24b2d 100644
--- a/docs/specification/draft/server/tools.mdx
+++ b/docs/specification/draft/server/tools.mdx
@@ -486,7 +486,7 @@ Embedded resources support the same [Resource annotations](/specification/draft/
 
 **Structured** content is returned as a JSON value in the `structuredContent` field of a result. This can be any JSON value (object, array, string, number, boolean, or null) that conforms to the tool's `outputSchema` if one is defined.
 
-For backwards compatibility, a tool that returns structured content SHOULD also return the serialized JSON in a TextContent block.
+For backwards compatibility, a tool that returns structured content SHOULD also return a TextContent block representative of the result data.
 
 #### Output Schema