Skip to main content
Use them so test runs never create real bookings or read live data, and so each test case gets the result it needs, such as “two slots open on Thursday” or “order not found”.

​
How it works

Mocking is set on the agent and applies to every simulation on that agent. Live traffic is never mocked.
  1. Open the agent’s Simulation Settings and turn on Mock tool calls. Every tool the agent has is listed.
  2. Pick a mode for each tool. Tools start on Generated.
  3. Run a simulation. Each tool call gets its answer from Bluejay.
The agent's Simulation Settings with Mock tool calls on and each tool set to Generated How the answer reaches your agent depends on the platform. ElevenLabs web and chat agents, and Google CES or Dialogflow CX tools that Bluejay runs, are mocked automatically. ElevenLabs phone and SIP, Retell, Vapi, Bland and custom agents need their tool server to ask Bluejay. See Setup by provider.

​
Override a tool for one test case

A Digital Human can override what a tool returns in its own runs. Edit the Digital Human and fill in Tool Response Overrides for the tool, JSON or plain text. Leave it empty to use the agent’s mode. A Digital Human's Tool Response Overrides with check_availability set to an empty slot list The order is: the Digital Human’s override, then the agent’s mode for the tool (Fixed or Generated), then your real backend. Overrides are separate from Tool Adherence. Tool Adherence grades which tools the agent calls; overrides only decide what the tools return.

​
Example

Your scheduling agent has check_availability and lookup_patient. You want to test that it reads back the times your calendar returns.
  1. Turn on Mock tool calls in the agent’s Simulation Settings.
  2. Set check_availability to Fixed with {"slots": ["Thursday 7:40 AM", "Thursday 4:05 PM"]}. Leave lookup_patient on Generated.
  3. Create a Digital Human who asks for a Thursday appointment, with the success criterion “The agent reads back the Thursday times that check_availability returned.”
When the agent looks up the caller, it gets back the Digital Human’s own details. When it checks availability, it gets Thursday at 7:40 AM and 4:05 PM and reads those times to the caller. No real calendar or patient record is read. To test a fully booked day in one test case, give that Digital Human an override for check_availability of {"slots": []}.

​
With the API or MCP

Turn mocking on, then set a tool to Fixed:
Overrides are the tool_responses field, an object keyed by tool name, when you create or update a Digital Human. With MCP or Bluejay AI, ask “mock tool calls for my scheduling agent”, then “make check_availability return Thursday 7:40 AM and 4:05 PM”. The tools are set_agent_mock_tools and set_agent_tool_mock.
Last modified on November 6, 2026