---
title: "Discussion on \"The tool cut off mid-JSON, and the agent filled the missing fields itself instead of stopping\" | Hashnode"
description: "Discussion on \"The tool cut off mid-JSON, and the agent filled the missing fields itself instead of stopping\". A tool call returned truncated JSON on timeout. The agent treated the partial chunk as live data and completed the missing fields by guess, so invented values blended into the plan. Covers why a model should never finish a partial record, and the raw-output checkpoint that stops it."
url: "https://hashnode.com/posts/tool-partial-json-agent-fills-missing-fields/6adf7f914f58eab0397db423"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The tool cut off mid-JSON, and the agent filled the missing fields itself instead of stopping](https://blogs.powerduck.com/tool-partial-json-agent-fills-missing-fields?utm_source=hashnode&utm_medium=feed)

A tool call returned truncated JSON on timeout. The agent treated the partial chunk as live data and completed the missing fields by guess, so invented values blended into the plan. Covers why a model should never finish a partial record, and the raw-output checkpoint that stops it.

Oct 26 · 3 min read · blogs.powerduck.com  
Read the article

-   [#mcp](https://hashnode.com/tag/mcp)
-   [#aicode](https://hashnode.com/tag/aicode)
-   [#aiagents](https://hashnode.com/tag/aiagents)
-   [#debugging](https://hashnode.com/tag/debugging)

## Written by

[Powerduck](https://hashnode.com/@powerduck)

@powerduck · hon

  
[View profile](https://hashnode.com/@powerduck)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
