5 ms·
you could for example create a skill to access your database for testing purposes and pass in your tables specifications so that the agent can easily retrieve d
by jonrosner 9mo ago
you could for example create a skill to access your database for testing purposes and pass in your tables specifications so that the agent can easily retrieve data for you on the fly.
- derrida 9mo agoOooooo, woah, I didn't really "get it" thanks for spelling it out a bit, just thought of some crazy cool experiments I can run if that is true.
- dkdcio 9mo agoit’s also for (typically) longer context you don’t always want the agent to have in its context. if you always want it in context, use rules (memories) but if it’s something more involved or less frequently used (perhaps some debugging methodology, or designing new data schemas) skills are probably a good fit
- hu3 9mo agoI made a small mcp script for database with 3 tools: - listTables - getTableSchema - executeQuery (blocks destructive queries like anything containing DROP, DELETE, etc..) I wouldn't trust a textual instructions to prevent LLMs from dropping a table.
- SatvikBeri 9mo agoThat's why I give the LLM a readonly connection
- wahnfrieden 9mo agoThis is much better than MCP, which also stuffs every session's precious context with potentially irrelevant instructions.
- kristo 9mo agoThey could just make mcps dynamically loaded in the same way no?
- wahnfrieden 9mo agoIt is still worse as it consumes more context giving instructions for custom tooling whereas the LLM already understands how to connect to and query a read-only SQL service with standard tools