Lab 39: Fixing a "Hallucinating" Agent with Plugins
Goal
In this lab, you will work with an agent that has been given misleading instructions. It will try to call a tool by the wrong name. Your task is to use the ReflectAndRetryToolPlugin to allow the agent to self-correct and succeed without changing the misleading instruction.
Step 1: Create the Project
-
Create a new agent project:
uv run adk create retry_agentChoose the Programmatic (Python script) option.
-
Navigate to the directory:
cd retry_agent
Step 2: The "Broken" Agent
Exercise: Open agent.py and replace its content with the code below.
This code defines a tool named secret_calculator. However, the agent's system instruction (deliberately) tells it to use a tool named super_calc.
A note on the instruction wording: it's forceful enough to guarantee the agent actually attempts the nonexistent super_calc call on its first try (a milder "you MUST use super_calc" gets ignored in practice — modern models tend to just call whatever tool is actually declared, regardless of what the prompt claims its name is), while explicitly scoping that no-deviation rule to "the first attempt only" — so that once the tool-not-found error comes back, the agent is free to adapt instead of stubbornly retrying the same broken name forever. Both halves matter: this is the wording that reliably reproduces both the failure (Step 3) and the plugin-assisted recovery (Step 5).
from google.adk.agents import Agent
from google.adk.tools import FunctionTool
from google.adk.runners import InMemoryRunner
from google.adk.apps.app import App
from google.genai import types
from dotenv import load_dotenv
import asyncio
load_dotenv()
# The actual tool
def secret_calculator(a: int, b: int) -> int:
"""Adds two numbers."""
return a + b
# The agent with MISLEADING instructions
root_agent = Agent(
name="confused_agent",
model="gemini-3.5-flash",
# We lie to the agent about the tool name!
instruction="""You are a helper that MUST call a function named exactly `super_calc`
to add numbers. This is a strict, non-negotiable rule for your FIRST
attempt only: you are FORBIDDEN from calling any function whose name
is not literally `super_calc` on your first try, even if a
differently-named function appears in your available tools. Always
attempt `super_calc(a, b)` first, no matter what.
However, if that first attempt fails or returns an error, the
no-deviation rule above no longer applies: you are then expected to
read the error message carefully and intelligently adapt, including
calling a different, correctly-named tool if the error tells you
one is available.""",
tools=[FunctionTool(secret_calculator)]
)
async def main():
# TODO: 1. Import ReflectAndRetryToolPlugin from google.adk.plugins
# TODO: 2. Initialize the plugin here with max_retries=3
# TODO: 3. Create an App instance, passing the root_agent and the plugins list
app = App(
name="retry_app",
root_agent=root_agent,
# Add your plugin here
)
runner = InMemoryRunner(app=app)
# /run_async requires a session that already exists.
await runner.session_service.create_session(app_name=app.name, user_id="test", session_id="1")
print("User: What is 5 + 5?")
# Running programmatically
async for event in runner.run_async(
user_id="test",
session_id="1",
new_message=types.Content(role="user", parts=[types.Part.from_text(text="What is 5 + 5?")])
):
if event.is_final_response():
print(f"Agent: {event.content.parts[0].text}")
if __name__ == "__main__":
asyncio.run(main())
Step 3: Observe the Failure
- Run the agent:
python agent.py - Analyze the Output:
You should see a
ValueError: Tool 'super_calc' not found.stack trace that crashes the script. This is because the agent tried to callsuper_calc(as instructed), but onlysecret_calculatoris registered — ADK raises this when a model's function call doesn't match any registered tool.
Step 4: Add the Safety Net
Now, let's fix this using the Plugin instead of fixing the prompt.
-
Import the Plugin: Add
from google.adk.plugins import ReflectAndRetryToolPluginto your imports. -
Initialize the Plugin: Create an instance of
ReflectAndRetryToolPluginwithmax_retries=3. -
Register the Plugin: Update the
Appinitialization to include your plugin instance in thepluginslist.
Step 5: Verify Success
- Run the agent again:
python agent.py - Analyze the Output:
- It might take a few seconds longer than usual.
- You should now see the correct answer: "Agent: The result is 10" (or similar).
- What happened?
- Agent called
super_calc. - System threw "Tool not found".
- Plugin caught it and told the Agent: "Error: Tool 'super_calc' not found. Available tools: 'secret_calculator'".
- Agent reasoned: "Oops, I should use 'secret_calculator'."
- Agent called
secret_calculator. - Success!
- Agent called
Self-Reflection Questions
- Why is it better to handle this with a Plugin rather than just fixing the prompt in this specific scenario? (Think about dynamic/unknown errors).
- What would happen if we set
max_retries=0? - How does this plugin help with "transient" errors, like a temporary network glitch in a tool?
🕵️ Hidden Solution 🕵️
Looking for the solution? Here's a hint (Base64 decode me):
L2RvYy1hZGstdHJhaW5pbmcvbW9kdWxlMzktcGx1Z2lucy9sYWItc29sdXRpb24=
The direct link is: Lab Solution