⚙️ Implementation: Should Vitto have its own web_search tool (Tavily) or rely o...

Date: 2026-02-24
Time: 15:04:57 UTC
Session: gspace1-138.10
Agent: backend
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Should Vitto have its own web_search tool (Tavily) or rely on http_request?

Task: Add Tavily web search to Vitto tool registry

🎯 Decision Made

Chosen:

Add dedicated web_search tool to Vitto's tool registry using Tavily API directly

Options Considered:

• No alternatives documented

💭 Reasoning

Vitto was blind to the internet — MCP agents had web_search but Vitto's tool registry didn't. Using http_request requires Vitto to know Tavily API format. A dedicated tool gives a clean interface (query, maxResults, searchType, includeDomains), matches MCP's web_search, and includes 5-minute caching. Uses same TAVILY_API_KEY env var. Available across all layers (developer, platform_builder, end_user). Placed in handlers/web-search.tool.ts following existing pattern.

📁 Files Involved

• apis/backend-vitto-api/src/app/tools/handlers/web-search.tool.ts
• apis/backend-vitto-api/src/app/tools/tool-registry.service.ts
• tools/scripts/database/env-loader.js

🔗 Related

• Decision ID: dev_1771945497026_afnipt4
• Session: 138
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation