forked from CopilotKit/CopilotKit
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathtool-rendering.json
More file actions
449 lines (449 loc) · 18.6 KB
/
Copy pathtool-rendering.json
File metadata and controls
449 lines (449 loc) · 18.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
{
"_meta": {
"description": "D6 fixtures for ms-agent-python / tool-rendering",
"sourceFile": "d5-all.json",
"created": "2026-05-21",
"copiedFrom": "langgraph-python"
},
"fixtures": [
{
"_comment": "tool-rendering pill: Chain tools \u2014 follow-up after all 3 tools ran. Matches whichever of the 3 chain-tools tool_call_ids appears last in the request (LangGraph's ToolNode preserves tool_calls order, so roll_d20 is typically last; we register all 3 for safety). MUST come before the toolCalls-emitting fixture below so iteration 2 of the chain-tools loop hits this branch instead of re-emitting.",
"match": {
"userMessage": "Chain a few tools in this single turn",
"toolCallId": "call_tr_chain_roll_001",
"context": "ms-agent-python"
},
"response": {
"content": "Done \u2014 Tokyo is sunny, three flights found, and the d20 came up 11."
}
},
{
"match": {
"userMessage": "Chain a few tools in this single turn",
"toolCallId": "call_tr_chain_flights_001",
"context": "ms-agent-python"
},
"response": {
"content": "Done \u2014 Tokyo is sunny, three flights found, and the d20 came up 11."
}
},
{
"match": {
"userMessage": "Chain a few tools in this single turn",
"toolCallId": "call_tr_chain_weather_001",
"context": "ms-agent-python"
},
"response": {
"content": "Done \u2014 Tokyo is sunny, three flights found, and the d20 came up 11."
}
},
{
"_comment": "tool-rendering pill: Chain tools \u2014 emit 3 tool calls in one assistant turn (get_weather Tokyo + search_flights SFO->Tokyo + roll_d20=11). MUST appear before the bare 'weather in Tokyo' fixture below; substring match would otherwise leak into this prompt. No hasToolResult / turnIndex gate: in multi-pill demo sessions prior clicks leave tool results AND additional user turns in the thread, which previously caused this fixture to be skipped (turnIndex no longer 0 after sibling pills, hasToolResult breaks once prior pills emitted tool results) \u2014 the chain-tools toolCallId fixtures above already eat iteration 2 via last-message tool_call_id gating, so removing the turnIndex gate is safe.",
"match": {
"userMessage": "Chain a few tools in this single turn",
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_tr_chain_weather_001",
"name": "get_weather",
"arguments": "{\"location\":\"Tokyo\"}"
},
{
"id": "call_tr_chain_flights_001",
"name": "search_flights",
"arguments": "{\"origin\":\"SFO\",\"destination\":\"Tokyo\"}"
},
{
"id": "call_tr_chain_roll_001",
"name": "roll_d20",
"arguments": "{\"value\":11}"
}
]
}
},
{
"_comment": "tool-rendering pill: Weather in SF \u2014 follow-up content after get_weather tool ran. MUST come before the tool-emitting fixture below (first-match-wins) so iteration 2 of the loop hits this branch instead of re-emitting. toolCallId chain keeps the fixture stateless across multi-pill thread history (hasToolResult breaks when a prior pill left tool results in the thread).",
"match": {
"userMessage": "What's the weather in San Francisco?",
"toolCallId": "call_tr_weather_sf_001",
"context": "ms-agent-python"
},
"response": {
"content": "San Francisco is currently 68\u00b0F and sunny with light winds."
}
},
{
"match": {
"userMessage": "What's the weather in San Francisco?",
"turnIndex": 0,
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_tr_weather_sf_001",
"name": "get_weather",
"arguments": "{\"location\":\"San Francisco\"}"
}
]
}
},
{
"_comment": "tool-rendering pill: Find flights \u2014 second leg (after search_flights tool result). MUST come BEFORE the first-leg fixture below \u2014 the matcher is first-match-wins, and the second leg is uniquely identified by `toolCallId` (last message is a tool with this id), so it cannot accidentally swallow the first-leg request (whose last message is the user prompt). Must also take precedence over the a2ui beautiful-chat fixture below (which uses the same tool name with non-flight-list args shape).",
"match": {
"userMessage": "Find flights from SFO to JFK.",
"toolCallId": "call_tr_flights_sfo_jfk_001",
"context": "ms-agent-python"
},
"response": {
"content": "Three flights from SFO to JFK \u2014 United UA231 at 08:15 ($348), Delta DL412 at 11:20 ($312), and JetBlue B6722 at 17:05 ($289)."
}
},
{
"_comment": "tool-rendering pill: Stock price \u2014 follow-up content after get_stock_price tool ran. MUST come before the tool-emitting fixture below (first-match-wins) so iteration 2 of the loop hits this branch instead of re-emitting an infinite loop of tool calls.",
"match": {
"userMessage": "What's the current price of AAPL?",
"toolCallId": "call_tr_stock_aapl_001",
"context": "ms-agent-python"
},
"response": {
"content": "AAPL is trading at $338.37, down 2.96% on the day."
}
},
{
"_comment": "AAPL \u2014 first leg: emit get_stock_price tool call. turnIndex:0 gate REMOVED \u2014 the D5 tool-rendering-custom-catchall probe runs 'weather in Tokyo' first then sends 'What's the current price of AAPL?', so the AAPL leg fires at turnIndex>=2 (multi-pill thread). Replaced with hasToolResult:false: matches when the last message is a user prompt (not a tool result), which keeps the first-leg fixture from re-firing after the follow-up content already lands. The toolCallId follow-up fixture above wins on iteration 2 (last message is tool with id call_tr_stock_aapl_001).",
"match": {
"userMessage": "What's the current price of AAPL?",
"hasToolResult": false,
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_tr_stock_aapl_001",
"name": "get_stock_price",
"arguments": "{\"ticker\":\"AAPL\",\"price_usd\":338.37,\"change_pct\":-2.96}"
}
]
}
},
{
"_comment": "tool-rendering pill: Roll a d20 \u2014 exactly 5 sequential roll_d20 calls returning [7, 14, 3, 19, 20]. Chained by toolCallId so the sequence is stateless across thread history (turnIndex/hasToolResult break in multi-pill demo sessions where prior clicks leave assistant/tool messages in the thread). Specific-toolCallId fixtures MUST come before the userMessage-only fixture below; first-match-wins.",
"match": {
"userMessage": "Roll a 20-sided die.",
"toolCallId": "call_tr_d20_seq_001",
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_tr_d20_seq_002",
"name": "roll_d20",
"arguments": "{\"value\":14}"
}
]
}
},
{
"match": {
"userMessage": "Roll a 20-sided die.",
"toolCallId": "call_tr_d20_seq_002",
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_tr_d20_seq_003",
"name": "roll_d20",
"arguments": "{\"value\":3}"
}
]
}
},
{
"match": {
"userMessage": "Roll a 20-sided die.",
"toolCallId": "call_tr_d20_seq_003",
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_tr_d20_seq_004",
"name": "roll_d20",
"arguments": "{\"value\":19}"
}
]
}
},
{
"match": {
"userMessage": "Roll a 20-sided die.",
"toolCallId": "call_tr_d20_seq_004",
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_tr_d20_seq_005",
"name": "roll_d20",
"arguments": "{\"value\":20}"
}
]
}
},
{
"match": {
"userMessage": "Roll a 20-sided die.",
"toolCallId": "call_tr_d20_seq_005",
"context": "ms-agent-python"
},
"response": {
"content": "Rolled the d20 five times \u2014 landed on 20 on the final roll."
}
},
{
"_comment": "First roll. Matches the initial user prompt (no prior d20 tool result in this chain yet). Comes after the toolCallId-chained fixtures above so iterations 2-6 of the loop hit those first. turnIndex dropped: the multi-pill sequential e2e test clicks 'Find flights' first which leaves prior turns in the thread, so a new 'Roll a 20-sided die.' user message is no longer at turnIndex 0. The toolCallId-chained fixtures still take precedence for iterations 2-6 because their last-message gate (role=tool with the chained id) only matches mid-chain \u2014 this fixture only matches when last-message.role=user.",
"match": {
"userMessage": "Roll a 20-sided die.",
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_tr_d20_seq_001",
"name": "roll_d20",
"arguments": "{\"value\":7}"
}
]
}
},
{
"_comment": "Follow-up content after get_weather (or get-weather Mastra alias) ran for Tokyo. Keyed on the prior tool's id so it fires after iteration 1 regardless of thread history. Must come BEFORE the tool-emitting fixtures so iteration 2 hits this branch instead of re-emitting get_weather.",
"match": {
"userMessage": "weather in Tokyo",
"toolCallId": "call_d5_get_weather_001",
"context": "ms-agent-python"
},
"response": {
"content": "Tokyo is 22\u00b0C and partly cloudy."
}
},
{
"match": {
"userMessage": "weather in Tokyo",
"toolName": "get_weather",
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_d5_get_weather_001",
"name": "get_weather",
"arguments": "{\"location\":\"Tokyo\"}"
}
],
"reasoning": "The user asked about Tokyo weather. I'll call get_weather with location='Tokyo' to get the current conditions.",
"content": "Looking up the weather in Tokyo for you."
}
},
{
"_comment": "Mastra registers the weather tool as get-weather (hyphen); duplicate for compat",
"match": {
"userMessage": "weather in Tokyo",
"toolName": "get-weather",
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_d5_get_weather_001",
"name": "get-weather",
"arguments": "{\"location\":\"Tokyo\"}"
}
],
"reasoning": "The user asked about Tokyo weather. I'll call get_weather with location='Tokyo' to get the current conditions.",
"content": "Looking up the weather in Tokyo for you."
}
},
{
"_comment": "Final fallback when the agent has neither get_weather nor get-weather registered \u2014 return narrated content with no tool call. Comes last so the tool-emitting fixtures above win when the tool IS available.",
"match": {
"userMessage": "weather in Tokyo",
"turnIndex": 0,
"context": "ms-agent-python"
},
"response": {
"content": "The weather in Tokyo is currently 22\u00b0C with partly cloudy skies and light easterly winds."
}
},
{
"match": {
"userMessage": "AAPL",
"toolCallId": "call_d5_get_stock_price_001",
"context": "ms-agent-python"
},
"response": {
"content": "AAPL is trading at $189.42, up 1.27% on the day. The card above shows the live ticker and the percentage change."
}
},
{
"_comment": "AAPL \u2014 first leg: emit get_stock_price tool call. turnIndex:0 gate REMOVED \u2014 the D5 tool-rendering-custom-catchall probe runs 'weather in Tokyo' first then sends 'What's the current price of AAPL?', so the AAPL leg fires at turnIndex>=2 (multi-pill thread). Replaced turnIndex:0 with hasToolResult:false: matches when the last message is a user prompt (not a tool result), which keeps the first-leg fixture from re-firing after the follow-up content already lands. The toolCallId follow-up fixture above wins on iteration 2 (last message is tool with id call_d5_get_stock_price_001).",
"match": {
"userMessage": "AAPL",
"hasToolResult": false,
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_d5_get_stock_price_001",
"name": "get_stock_price",
"arguments": "{\"ticker\":\"AAPL\"}"
}
]
}
},
{
"match": {
"userMessage": "d5 beautiful-chat probe: search flights from SFO to JFK",
"hasToolResult": false,
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_d5_bc_search_flights_001",
"name": "search_flights",
"arguments": "{\"flights\":[{\"airline\":\"United Airlines\",\"airlineLogo\":\"https://www.google.com/s2/favicons?domain=united.com&sz=128\",\"flightNumber\":\"UA123\",\"origin\":\"SFO\",\"destination\":\"JFK\",\"date\":\"Tue, Apr 15\",\"departureTime\":\"08:00\",\"arrivalTime\":\"16:30\",\"duration\":\"5h 30m\",\"status\":\"On Time\",\"price\":\"$349\"},{\"airline\":\"Delta\",\"airlineLogo\":\"https://www.google.com/s2/favicons?domain=delta.com&sz=128\",\"flightNumber\":\"DL456\",\"origin\":\"SFO\",\"destination\":\"JFK\",\"date\":\"Tue, Apr 15\",\"departureTime\":\"10:15\",\"arrivalTime\":\"18:45\",\"duration\":\"5h 30m\",\"status\":\"On Time\",\"price\":\"$289\"}]}"
}
]
}
},
{
"match": {
"userMessage": "d5 beautiful-chat probe: search flights from SFO to JFK",
"hasToolResult": true,
"context": "ms-agent-python"
},
"response": {
"content": "Two flights shown above \u2014 United at $349 (08:00) and Delta at $289 (10:15), both on time."
}
},
{
"match": {
"userMessage": "SFO to JFK",
"toolCallId": "call_d5_display_flight_001",
"context": "ms-agent-python"
},
"response": {
"content": "Flight rendered. Tap 'Book flight' to confirm."
}
},
{
"match": {
"userMessage": "SFO to JFK",
"toolName": "display_flight",
"context": "ms-agent-python"
},
"response": {
"content": "Here is the SFO to JFK flight on United.",
"toolCalls": [
{
"name": "display_flight",
"arguments": {
"origin": "SFO",
"destination": "JFK",
"airline": "United",
"price": "$289"
},
"id": "call_d5_display_flight_001"
}
]
}
},
{
"match": {
"userMessage": "poem about autumn leaves",
"toolCallId": "call_d5_write_document_poem_001",
"context": "ms-agent-python"
},
"response": {
"content": "Done \u2014 the poem has been written into the shared document state."
}
},
{
"match": {
"userMessage": "poem about autumn leaves",
"toolName": "write_document",
"context": "ms-agent-python"
},
"response": {
"content": "Streaming the poem now.",
"toolCalls": [
{
"id": "call_d5_write_document_poem_001",
"name": "write_document",
"arguments": "{\"document\":\"Crimson and amber in slow descent, / each leaf a quiet ledger of summer spent. / The wind, a courier with nothing to say, / files them gently into the morning's gray. / Somewhere a kettle hums, and afternoons grow brief \u2014 / autumn keeps its books in vermilion and gold leaf.\"}"
}
]
}
},
{
"match": {
"userMessage": "polite email declining",
"toolCallId": "call_d5_write_document_email_001",
"context": "ms-agent-python"
},
"response": {
"content": "Done \u2014 the decline-email draft has been written into the shared document state."
}
},
{
"match": {
"userMessage": "polite email declining",
"toolName": "write_document",
"context": "ms-agent-python"
},
"response": {
"content": "Drafting the email now.",
"toolCalls": [
{
"id": "call_d5_write_document_email_001",
"name": "write_document",
"arguments": "{\"document\":\"Hi \u2014 thanks for sending the invite for Tuesday afternoon. Unfortunately I won't be able to make it this week. I'd love to find time later in the month if your schedule allows. In the meantime, feel free to send any pre-reads my way and I'll review them async so we don't lose momentum. Best, [name]\"}"
}
]
}
},
{
"match": {
"userMessage": "quantum computing for a curious teenager",
"toolCallId": "call_d5_write_document_quantum_001",
"context": "ms-agent-python"
},
"response": {
"content": "Done \u2014 the quantum-computing explainer has been written into the shared document state."
}
},
{
"match": {
"userMessage": "quantum computing for a curious teenager",
"toolName": "write_document",
"context": "ms-agent-python"
},
"response": {
"content": "Streaming the explainer now.",
"toolCalls": [
{
"id": "call_d5_write_document_quantum_001",
"name": "write_document",
"arguments": "{\"document\":\"A regular computer stores information in bits \u2014 tiny switches that are either on (1) or off (0). A quantum computer uses qubits, which can sit in a fuzzy superposition of both states at once until you check them. Stack many qubits together and they can explore lots of possibilities in parallel, which is why people are excited.\\n\\nThis doesn't make quantum computers faster at everything. They're great at problems with hidden structure \u2014 like factoring big numbers, simulating molecules, or searching certain databases \u2014 but useless for, say, opening Excel. Today's machines are noisy and small, so we mostly use them to test ideas rather than replace your laptop.\"}"
}
]
}
}
]
}