OPEN_SOURCE ↗
REDDIT · REDDIT// 11d agoINFRASTRUCTURE
lazy-tool trims MCP prompt bloat
lazy-tool is a local-first MCP tool discovery runtime that keeps a local catalog of tools and surfaces only relevant ones at request time. It targets the prompt-bloat problem in MCP-heavy agent setups, especially for smaller local models and workflows with large tool inventories.
// ANALYSIS
This is a pragmatic infrastructure fix for a real failure mode in agent systems: once tool catalogs get large, “just stuff everything into the prompt” stops scaling, and smaller models suffer first.
- –Search-before-invoke is the right default for weak or local models because it reduces context load without giving up tool access
- –The single Go binary plus SQLite approach keeps the runtime simple and deployable on a laptop, not just in a larger agent stack
- –Auto-import from Claude Desktop, Cursor, and VS Code lowers setup friction, which matters more than another abstract registry idea
- –The direct/search/hybrid modes are useful because they acknowledge that one tool-loading strategy will not fit every model class
- –The benchmark angle is the strongest part of the pitch, but the product will need broader real-world comparisons to prove it beats simpler per-agent filtering schemes
// TAGS
lazy-toolmcpcliself-hosteddevtoolagent
DISCOVERED
11d ago
2026-03-31
PUBLISHED
11d ago
2026-03-31
RELEVANCE
8/ 10
AUTHOR
geeganage