Avoid designing tasks that modify the main codebase so it’s clear which files are are intended for user modification and which files are to be "used" by the agent. For example, we can create a dedicated "sandbox" folder where agents perform all operations.
Activities may be challenging for people who have no background in MCP. Suggested activities if we rerun the workshop:
- Demo: City Explorer Agent (the "Weather" tool of the city) [originally stage 0 demo; a dummy tool that always return 25 degree]
- Code: Showing step-by-step how to code the City Explorer Agent and the weather tool from scratch [adapted from stage 0 demo]
- Code: Add another tool (e.g., "Get current time") to the City Explorer Agent [adapted from stage 0 demo]. This can be a tool that returns the current time on the computer. Better yet, instruct the model to return the time considering the time difference of the city.
- Demo: MCP server--explore the sandbox (ls, pwd, cd commands) [adapted from stage 2]
- Code: Modify the code so it supports additional commands (cat, head, tail) to explore the content of the file [adapted from stage 2]
- Demo: Multi-agent orchestration--see if we have a scenario that can relate to more students [adapted from stage 3]
Avoid designing tasks that modify the main codebase so it’s clear which files are are intended for user modification and which files are to be "used" by the agent. For example, we can create a dedicated "sandbox" folder where agents perform all operations.
Activities may be challenging for people who have no background in MCP. Suggested activities if we rerun the workshop: