Structured Output vs MCP Structured Tool Output
People think both mean the model writes neat JSON. Only one does. Structured output is a model's own answer, forced into a set shape. MCP structured tool output is data a tool sends back after it runs, in a field called structuredContent. The model did not write it at all. One shapes what the model says, the other shapes what a tool returns.
Structured Output (LLM)
The model's answer must fit a set shape, like JSON with set fields.
Structured output makes a model's answer follow a fixed shape, most often JSON that matches a schema you give. A schema lists the fields, their types and which ones are needed. Many model APIs can enforce it, so the reply always fits. That lets a program read the answer with no guessing. Without it, a model may add chatty text or drop a field, and the program breaks.
MCP Structured Tool Output
Tool results sent as neat data in a set shape. Code can read them.
MCP structured tool output is data a tool returns in a set shape, not just as text. The tool can declare an output schema that says what that shape is. Its result then carries the data in a field called structuredContent. For older clients, the tool should also return the same data as text. Code can read the data straight away, with no guessing from words.
In one line
- Structured Output (LLM)
- The model's answer must fit a set shape, like JSON with set fields.
- MCP Structured Tool Output
- Tool results sent as neat data in a set shape. Code can read them.