Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/694057b6-101c-8007-9a65-c40578c7252d
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==== 13. Tools and exit tools ==== ===== Normal tools (round-trip) ===== * OpenAI function/tool calling schema. * Executed via pluggable ToolRunner. * Budget is iterations, not calls: - one assistant tool-emission that contains any normal tool calls consumes exactly 1 iteration, even if it requests multiple tools at once. * Fallback parsing is allowed when structured tool_calls are absent/unreliable (BIOS-guided strict JSON). ===== Tool failure classification (locked) ===== Tools should only kill the request when there is an actual execution/format problem, such as: * tool runner timeout, * tool runner exception, * malformed tool arguments (parse/validation), * non-serializable result (implementation error), * unknown tool name. Domain outcomes are not failures: * e.g. “search found nothing” must be a successful tool result (empty list / {results: []} / {found: false}), and the request continues. ===== Exit tools (one-way signals; non-terminating) ===== * Exit tools are provided at worker init as tool definitions. * Worker exposes them to the model and records any exit-tool calls as structured signals[]. * Exit tools are never executed (no ToolRunner) and never alter control flow. * Priority: process normal tool loop as usual; record exit signals whenever they occur. * Models will be encouraged (via BIOS) to emit exit tools near completion, but correctness does not depend on it.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)