Unverified50% confidenceFactExact time
When the model calls an unknown tool or passes input that does not match the schema, WorkflowAgent's stream() now retains that tool call, marks it as invalid, and produces a tool-error part in the step, matching the behavior of generate() and ToolLoopAgent; the model still receives the error as the tool result.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/13/2026
First Seen
Valid until: 2/11/2027
Sources
Related Entities
Related Claims
UnverifiedIn WorkflowAgent, a tool call rejected by toolApproval receives an execution-denied tool result but does not pause the entire workflow.73% similarUnverifiedThe content blocks at the interface layer are not equivalent to the tool call representation inside the inference framework: the former is a protocol convention for cross-process transmission, the latter is an intermediate structure in the model runtime, and mapping errors cause loss of tool semantics.71% similarUnverifiedIn systems with tools attached, if the model can call APIs, send messages, write to databases, or execute code, injected instructions that get executed may cause irreversible consequences.71% similarUnverifiedWorkflowAgent's toolApproval configuration can be passed in the constructor or on each generate() or stream() call, and it takes precedence over the tool's own needsApproval setting.70% similarUnverifiedCommit 6ac1ee1 makes WorkflowAgent use the original tool schema to validate and normalize tool input, thereby staying consistent with streamText behavior.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1168541API
curl https://kongchang.com/api/v1/knowledge/claims/1168541MCP
get_claim(id=1168541)