From a9eed9b1cdcc37e4a21c63d1c52d0b1e9a8a1c10 Mon Sep 17 00:00:00 2001
From: Benjamin Frost <58258541+benjamin-frost@users.noreply.github.com>
Date: Wed, 19 Nov 2025 14:23:12 +0100
Subject: [PATCH] docs: clarify ProviderStrategy vs ToolStrategy in
response_format note
---
src/oss/langchain/structured-output.mdx | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/oss/langchain/structured-output.mdx b/src/oss/langchain/structured-output.mdx
index 71eb3c34a6..a930851254 100644
--- a/src/oss/langchain/structured-output.mdx
+++ b/src/oss/langchain/structured-output.mdx
@@ -272,12 +272,12 @@ Provider-native structured output provides high reliability and strict validatio
:::python
- If the provider natively supports structured output for your model choice, it is functionally equivalent to write `response_format=ProductReview` instead of `response_format=ToolStrategy(ProductReview)`. In either case, if structured output is not supported, the agent will fall back to a tool calling strategy.
+ If the provider natively supports structured output for your model choice, it is functionally equivalent to write `response_format=ProductReview` instead of `response_format=ProviderStrategy(ProductReview)`. In either case, if structured output is not supported, the agent will fall back to a tool calling strategy.
:::
:::js
- If the provider natively supports structured output for your model choice, it is functionally equivalent to write `responseFormat: contactInfoSchema` instead of `responseFormat: toolStrategy(contactInfoSchema)`. In either case, if structured output is not supported, the agent will fall back to a tool calling strategy.
+ If the provider natively supports structured output for your model choice, it is functionally equivalent to write `responseFormat: contactInfoSchema` instead of `responseFormat: providerStrategy(contactInfoSchema)`. In either case, if structured output is not supported, the agent will fall back to a tool calling strategy.
:::