Unverified50% confidenceFactExact time
In the tool runner, after append_messages() the history is now managed by the caller.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/23/2026
First Seen
Valid until: 1/21/2027
Sources
Related Entities
Related Claims
UnverifiedWhen set_messages_params() provides tools in definitions form, the tool runner continues to run its function tools; once a tool is removed from tools, the runner no longer executes it.70% similarUnverifiedEvery gateway interaction should produce a structured record containing trace_id, user_id, timestamp, model name, input/output token counts, latency, policy violations, and a list of tool calls, with the trace ID used to correlate multiple fanned-out calls.69% similarUnverifiedTool calling refers to the mechanism by which an Agent requests the execution of an external function through a structured message and has the result returned; the returned content enters the conversation history as a message with role: 'tool' and from then on permanently occupies the context.69% similarUnverifiedThe new version of the AI agent logs tool calls to the `session_message` table rather than the `part` table.69% similarUnverifiedIn v1.5.0, messages.create, parse, stream, and count_tokens can now directly accept tool objects without manually converting them to a specific parameter structure.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1089698API
curl https://kongchang.com/api/v1/knowledge/claims/1089698MCP
get_claim(id=1089698)