Show HN: Lazy-tool: reducing prompt bloat in MCP-based agent workflows
like-to-code1
20 points
2 comments
March 31, 2026
Related Discussions
Found 5 related stories in 81.6ms across 3,471 title embeddings via pgvector HNSW
- Show HN: A prompt that builds the most capable AI agent system fainir · 12 pts · March 28, 2026 · 64% similar
- Show HN: Mcp2cli – One CLI for every API, 96-99% fewer tokens than native MCP knowsuchagency · 144 pts · March 09, 2026 · 57% similar
- Show HN: Real-time dashboard for Claude Code agent teams simple10 · 70 pts · April 01, 2026 · 56% similar
- Show HN: Real-time observability for coding agents vtemian · 14 pts · March 17, 2026 · 56% similar
- Show HN: Understudy – Teach a desktop agent by demonstrating a task once bayes-song · 96 pts · March 12, 2026 · 54% similar
Discussion Highlights (1 comments)
mitul005
Nice work. How does this compare to running a Go-based MCP proxy like lazy-mcp? The core tradeoff I'm curious about is whether deferring tool schema loading at the protocol level is more reliable than filtering at the agent prompt level.