Repository navigation
Quality vs quantity #568
Replies: 2 comments 2 replies
|
I don't know except the tools I use work reasonably well. I'm working on reigning in code growth and started on combining tools, removing dead code, fixing bugs. |
0 replies
|
The count is going down, not up: dev is at 210 tools after #567 and #570 folded overlapping ones together (find_functions replaced five listing/search tools, list_program_items replaced eight), and #577 merges the two documentation writers next. There's no per-tool quality score yet. What exists: an offline suite that checks every call against the schema, a contract test that catches parameter names no tool accepts, and a live regression run required before each release. A per-tool reliability number is a fair ask and I'd like to add one. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello!
Ive seen this grow from "laurie" to 110 to 253 tools... And same with treesitter language pack and many others where AI explode the capabilities surfaces but often very shallow.
And im wondering... If the metric was not amount of tool calls... And it instead was focused on quality?
What would the score be for those 253?
All reactions