220 karma · joined June 17, 2022
But if im running a customer support agent at scale, i'm not sure I want it to be able to write code. I do know I need it to be able to convert timezones though. (its also far more expensive / token inefficient to have it write code each time to convert timezones rather to use a predefined tool I made an know works)
okay, but now my agent needs a coding environment / sandbox.
MCP (or tool use in general) solves this without that (extremely tenuous and expensive to do at scale in prd) requirement.
The skill is totally orthogonal here--solving a totally separate problem
I want my agent to be able to convert reliably between timezones. A skill does not solve this. It needs a deterministic tool it can call
you pass in your "prompt" and options (described in natural language) that it can respond with, in addition to your input. it gives back that option set with a probability assigned to each one
calling my whole site AI slop is a bit rude but mostly just wrong. I have put in a lot of work to my posts and my projects.
and, > "I don’t think the author could explain what the second part of the article is supposed to mean"
??? its a bit. half the post is a bit. im leaning into it. _The weights were revealed inside a harness_ is literally glowing. wdym i cant explain any of it
google's inability or unwillingness to provide stable timelines for model deprecation makes it risky to build complex workflows using their models
how do you think it works today? some guy with binoculars?
It sounds like you don't like LLMs! In that case, you may be more interested in our REST Api. All the same functions, but designed for edge computing, where dependency bloat is a real issue https://tinyfn.io/edge