Skip to content

Kitchen-Aide Agent 🍳

In this notebook, you'll learn how Conditional Requirements shape what tools an agent can see and use on each turn. Using a playful Kitchen-Aide Agent, you'll explore how developer-defined rules can restrict, allow, or sequence tool access.

🥘 Workshop Scenario

Your Kitchen-Aide Agent helps you make cooking decisions using:

  • Your fridge, freezer, and pantry inventory tools
  • Your personal recipe search
  • An optional internet recipe tool

You'll ask questions like:

  • "What can I make with what I already have?"
  • "What ingredients am I missing for this recipe?"
  • "Is there a web recipe that fits my ingredients?"

The key lesson: conditional requirements decide which of these tools the LLM is even allowed to call on each turn.

📚 What You'll Learn

⭐ Conditional Requirements

You'll implement rules such as:

  • A tool can be used only once (e.g., get_fridge)\
  • Certain tools are hidden until another tool has been used\
  • A tool may require a specific argument before the LLM can call it\
  • A tool may be temporarily unavailable depending on state

These rules can either force a workflow or simply expose or hide tools based on developer-defined conditions.

🚀 Getting Started

Quick Setup

  • Google Account – Required for accessing Google Colab
  • Workshop Notebook – Open the notebook Open In Colab
  • Personal Copy – If you'd like to save your changes, please copy this notebook and create your own version

Then:

  • Configure your agent and tools
  • Add Conditional Requirements
  • Test how the agent's accessible tools change as you interact

Learn More About BeeAI