CTO, Co-Founder, @tryArcade | @redisinc @HPE_Cray | AI, LLM, Python, HPC, ⚾️ fan, roll tide | Blog: https://xitter.cf/t.co/PJfL2cMCYD | Opinions are my own.
San Francisco, CA
Joined April 2013
- Tweets1.4K
- Following463
- Followers1.7K
- Likes4K
Sam Partee retweeted
Look Ma, we made it again! 🎉
I have a new peer reviewed paper on @arxiv: Tool Recommendation for Multi-Step Agents: Finding Every Tool a Task Needs
Written with the @TryArcade crew: @SamPartee, River Stevens, and Valerie Fanelle.
We started out trying to figure out “how do we give agents the whole ~8k tool catalog without the context window or the bill exploding.”
Ended up with a real deployed system with some pretty nice numbers:
• First recommendation covered every required tool in 93% of Codex sessions
• 57% better top-10 coverage than BM25 on ToolRet
• Cut input tokens 17–40% and the bill by up to 40% vs a fixed list of 100 tools (no drop in task completion)
Link to full paper in the comments
Sam Partee retweeted
@SamPartee , River Stevens, @ptdamiba, and Valerie Fanelle put the research behind Arcade.dev’s Tool Recommendation on arXiv. These are the details behind all the token cost reduction and ToolRet scoring. For the nerds: arxiv.org/abs/2610.23707
Sam Partee retweeted
This week in Chicago, Arcade.dev CTO @SamPartee and Sabry Loganathan of @onepeloton talked through governing enterprise agents in production, from identity models and multi-user policies to the lessons they wish they'd known before scaling past the pilot.
We're hoping to get them on a stage together again soon.
Sam Partee retweeted
Thanks to @VentureBeat for the exclusive on Tool Recommendation’s launch. @carlfranzen nailed the problem it solves: “Connecting an agent to more business systems also makes its instructions larger and more expensive.”
venturebeat.com/orchestratio…
Sam Partee retweeted
We're "already fixing that."
@VentureBeat covered five startups building infrastructure for enterprise agents. Our CTO @SamPartee on the three snags agents hit authorization, governance, and reliability and why acting on behalf of real users takes a different security architecture:
venturebeat.com/orchestratio…
Sam Partee retweeted
Agent identity was always the goal for @SmitheryDotAI.
We talked about it in our blog posts about building "Google for a new internet", the new internet being one in which tool calls outpace human clicks.
With @TryArcade being deployed at multiple F100s including big six megabanks (and raising a $60m series A!), they've found the clearest path to enterprise value in the same space.
Thrilled to be joining such a capable team to bring the Smithery developer experience to the enterprise, and the enterprise-grade robustness and security to the Smithery platform :)
@SmitheryDotAI, the leading public registry and hosting platform for MCP, is now part of Arcade.dev.
Smithery made finding and running an MCP server take one click. Pairing that developer experience with the security, reliability, and governance that Arcade is known for, gives enterprises both to lead the next generation of agentic AI.
Smithery co-founder @kamathematic is joining us to keep building it.
More from @TheMostlyGreat: arcade.dev/blog/smithery-joi…
Smithery 🤝 Arcade
So excited for this and to work with @kamathematic
So begins the path to eating the agent stack from the bottom up
@SmitheryDotAI, the leading public registry and hosting platform for MCP, is now part of Arcade.dev.
Smithery made finding and running an MCP server take one click. Pairing that developer experience with the security, reliability, and governance that Arcade is known for, gives enterprises both to lead the next generation of agentic AI.
Smithery co-founder @kamathematic is joining us to keep building it.
More from @TheMostlyGreat: arcade.dev/blog/smithery-joi…
The second you find yourself switching away to another medium to do the work, your agent has a capability gap.
Sam Partee retweeted
July 28 is the largest MCP spec update to date. We’ve covered stateless and auth. Next up: extensions.
Notice that no client is obligated to support any extension and authors can ship breaking changes on their own cadence.
A tool that works in Claude might not work in Cursor.
Read more for the full breakdown: arcade.dev/blog/mcp-extensio…
notably their oss does better than some companies with serious funding to *just do this*. Slept on. @BraceSproul