MCP supports loading tools after the session has started (although client support is not universal yet). We can leverage this by not loading the full tool set at the start and instead having a loader tool for the agent to call on. This can enable tools like our encoding utilities to avoid using context unless actual encoding / decoding is needed. Or crawler could avoid being loaded unless specifically the explore workflow is selected by the agent.
Not a critical feature right now with our current API complexity, but in the future (also when client support is more universal) this is worth investigating.
MCP supports loading tools after the session has started (although client support is not universal yet). We can leverage this by not loading the full tool set at the start and instead having a loader tool for the agent to call on. This can enable tools like our encoding utilities to avoid using context unless actual encoding / decoding is needed. Or crawler could avoid being loaded unless specifically the
exploreworkflow is selected by the agent.Not a critical feature right now with our current API complexity, but in the future (also when client support is more universal) this is worth investigating.