feat(models_ollama): Include model capabilities - #623
Merged
Merged
Conversation
hadley
approved these changes
Jul 7, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm on a plane and didn't have WiFi, which reminded me that one bit of friction with local models via Ollama is that I can never remember which models have tool calling capabilities.
It turns out that you can query a model's details via the
/api/showendpoint. I thought this would be useful information to have, so I used this to add acapabilitiescolumn tomodels_ollama(). Having to query one-at-a-time slows down the call tomodels_ollama()at about 10ms per model (on my Macbook Air M3), but we can cache model details to avoid paying for the model details more than once.