The idea of "model controlled", "application controlled" and "user controlled" for tool, resources and prompts (respectively) was aligned with the chat interface. It breaks for the autonomous agent paradigm where the agency is the user and the lines are blurred. Unfortunately MCP has been mostly relegated to tool calling leaving potentially powerful capabilities on the table due to lac of client support for them.
"In a shocking finding, scientist discovered a herd of unicorns living in a remote, previously unexplored valley, in the Andes Mountains. Even more surprising to the researchers was the fact that the unicorns spoke perfect English."
This is my experience as well. It gets worse when the LLMs have strong priors in subject matter adjacent to your novel work. The generated output will incorrectly pull towards things the LLM has seen in it’s training data.
I'm working on leveraging NLP and LLM techniques to create a geometry over the discrete space of Ethereum transaction execution structure. (sorry... it's a bit of a mouthful)
You may be thinking of Litestar (previously named Starlite) that was based on Starlette akin to FastAPI but then went their own direction implementing a framework rather than relying on an upstream for their core product.
Fine tuning Gemini 2.5 flash on EVM Blockchain execution structures and using perplexity with PageRank to perform transaction anomaly detection.
https://lite.chaingenius.ai/theory
Odd seeing this right now for me. I recently implemented a 6NF schema for parsed XBRL files from EDGAR. The architecture was the right call... too bad the data is not useful for analytics.
reply