4 ms·
> In my view, we hand craft the context and then the LLM makes the deductions. We (as in users) provide the source material and our questions, the LLM provides
by kiitos 1y ago
> In my view, we hand craft the context and then the LLM makes the deductions.
We (as in users) provide the source material and our questions, the LLM provides the answers. The entire concept of a context is incidental complexity resulting from technical constraints, it's not anything that users should need to care about, and certainly not something they should need to craft themselves.
- the_other 1y agoBut it makes a radical difference to the quality of the answer. How is the LLM (or collaboration of LLMs) going to get all the useful context when it’s not told what it is? (Maybe it’s obvious in how MCP works? I’m only at the stage of occasionally using LLMs to write half a function for me)
- kiitos 1y agoIn short, that's the job of the software/tooling/LLM to figure out, not the job of the user to specify. The user doesn't know what the context needs to be, if they did and could specify it then they probably don't need an LLM in the first place. MCP servers are a step in the direction of allowing the LLM to essentially build up its own context, based on the user prompt, by querying third-party services/APIs/etc. for information that's not part of their e.g. training data.