How vox304/vinuni_codelab_day04_template works
This is a small educational chatbot/tool-calling lab scaffold. Its demonstrated workflow is a demo runner invoking a mock baseline and a stub agent; the agent’s intended intent analysis and tool loop are TODOs, so no agent-to-tool calls are shown. The product also defines catalog-search and support-ticket tools, with corresponding JSON files named as their intended data stores. Those operations are likewise unimplemented. The README is empty, so capability and relationship evidence comes from the sampled source only.
Main entry points: tools.py Tool schemas and map · template.py Demo runner
Components 8
Chat modes
- Demo runner
starter-code/template.py - Baseline chatbot
starter-code/template.py - Tool-calling agent
starter-code/template.py
Tool layer
- Tool schemas and map
starter-code/tools.py - Catalog search
starter-code/tools.py - Ticket submission
starter-code/tools.py
Local data
- Product catalog
raw-data/product_catalog.json - Support tickets
raw-data/support_tickets.json
Connections 5
- Demo runner → Baseline chatbot: invokes
starter-code/template.py - Demo runner → Tool-calling agent: invokes
starter-code/template.py - Tool-calling agent → Tool schemas and map: imports
starter-code/template.py - Tool schemas and map → Catalog search: maps to
starter-code/tools.py - Tool schemas and map → Ticket submission: maps to
starter-code/tools.py