Agents

Control the next step of the maintenance assistant

BOTIE

Require used to be below limit and status to equal ok. Produce one boolean continuation flag.
Ready to test
0 passed · 0 failed · 3 not run

An empty floor. Start with the information your machine needs.

Received result

Your answer will arrive here.

Examples, experiments and workspace controls
Live values

Connect a tool's inputs to see what it produces. You can try a branch before connecting it to Result.

Try your own inputs

Use a copy of the example to try your own data. Keep the problem's assumptions in mind, and predict the effect of a change before checking the output. You can also add another branch to compare two ways of doing the calculation.

Start at an output arrow, then click or drag to an input. Drag empty space to pan. Delete removes a selection. Ctrl/Cmd+Z undoes a change.
Context for this challenge

Require used to be below limit and status to equal ok. Produce one boolean continuation flag.

Botie receives another proposed action after a tool observation. The application must decide whether to return a final response, allow a tool, or hand off.

Inspect the component calculation
Require both checks(
  First check: Check below a limit(
    Current value: Tool attempts already used
    Limit: Maximum tool attempts
  )
  Second check: Compare complete values(
    First value: Last tool status: ok or permanent_error
    Second value: Text value(
      Text: ok
    )
  )
)
Examples and results
Tool attempts already used
1
Maximum tool attempts
3
Last tool status: ok or permanent_error
ok
Required result
true
Tool attempts already used
2
Maximum tool attempts
2
Last tool status: ok or permanent_error
ok
Required result
false
Tool attempts already used
1
Maximum tool attempts
3
Last tool status: ok or permanent_error
permanent_error
Required result
false
Try a fresh construction

This clears this draft, including its undo history. Earlier successful attempts stay recorded. Build again without opening hints to record an independent attempt.

Stuck? Inspect a worked construction

The tools below form one possible solution. You can assemble it, follow its signals, and undo that change to return to your own construction.

Assumptions and test precision

This is one deterministic controller decision, not a model inference. The host must separately validate final answers and enforce time, token, permission and side-effect limits. Numerical tests allow a difference of 0.001. Lists and structures must also have the right shape.

Your last tested pieces can start the full construction. An existing draft there keeps its own pieces.

This request has no tool allowance

This check uses the pieces from “Decide whether another tool is allowed”.

BOTIE

Botie proposes a tool before any tool has run, but this request is configured with a tool-attempt limit of zero. The previous status is ok. Decide the next branch.
Validated next proposal: tool or finish
tool
Tool attempts already used
0
Maximum tool attempts
0
Last tool status: ok or permanent_error
ok

Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.

Build a construction in the workspace above first. This case will test those pieces.

What does a successful scripted replay tell you about a live model’s choice of tools?

It verifies the controller on supplied events. Evaluate model choices and answer quality separately, using the same observable action and result records.

This is one deterministic controller decision, not a model inference. The host must separately validate final answers and enforce time, token, permission and side-effect limits.

Work through the Python challenges →
Continue the courseDoes Botie Need to Choose the Next Step? →