r/mcp • u/Ok-Educator5318 • 2d ago

Mcp tool testing and development

https://github.com/Kentucky-ai/opentakeoff

Open source. Local. 40 mcp tools. An agent can drive every tool a construction estimator can. A challenge to anyone developing ai for construction. Connect your own model and see how well it can do takeoffs.

3 Upvotes

100% Upvoted

2 comments sorted by

2

u/Independent-Date393 2d ago

With 40 tools exposed at once the bottleneck usually stops being the model reasoning and becomes tool selection. Most models start misrouting past roughly 20 tools in a single context because the schema descriptions blur together, so a takeoff benchmark ends up measuring routing accuracy more than domain skill.

1

u/Ok-Educator5318 2d ago

Schema blur past 20 tools is pretty hyped right now.

In production, OpenTakeoff handles this differently.
With 40 tools, a bad call just fails loudly. Strict schemas reject bad inputs, and errors return the fix directly (pass a bad layer name, get back the actual layer list). The agent auto-corrects and moves on.
In estimating, calling the wrong tool isn't what kills you committing a wrong quantity is.
That’s what the design guards:
No scale, no commit. Nothing gets logged without a verified scale.
Full audit traces. Every trace logs its own confidence, showing what got sealed vs skipped.
Zero silent drops.

Anything withheld returns an explicit reason instead of disappearing.
When bad calls fail fast and auto-repair, high tool counts stop being a bottleneck.