Video wird geladen...
Video konnte nicht geladen werden
Storing too many tools in your context window increases latency and can lead to wrong tool selection. In this demo, we used LFM2.5-ColBERT-350M as a filter to only select the five most relevant tools among 151 options. It's fast and reliable, even without any specific fine-tuning. Try the demo... show more
33,824 Aufrufe • vor 3 Monaten •via X (Twitter)
12 Kommentare

Why LFM2.5-ColBERT-350M and not LFM2.5-Embedding-350M? Isn’t a single vector good enough for tool selection? It’s simpler to implement too I assume.

Tiny but powerful, that’s what I usually describe LFMs

I guess this will fit perfectly in my recent research : "

How can we test with the API of the LFM 2.5 8B model?

@maximelabonne @tejus_sawjiani

W

curious how tight the correlation is between colbert rank and tool correctness. feels like a good spot to find weird model behaviors and test some reranking ideas.

Filtering to the 5 most relevant tools out of 151 without fine-tuning is impressive 👏

Smart move - 151 → 5 tools = less lag, better picks LFM2.5-ColBERT-350M filtering without fine-tuning is clutch.

This fixes a massive structural headache for agentic workflows.

151 tools is wild. filtering down to 5 keeps things snappy. how does it score ties when tool descriptions overlap hard

Smarter tool selection, zero latency bloat

