Tools list serialization to enable separation of model and application execution engines

[skamalj]

Checked

• I searched existing ideas and did not find a similar one
• I added a very descriptive title
• I've clearly described the feature request and motivation for it

Feature request

I have been trying to work with langgraph in a way where model.invoke is separated out into a gateway. Primary motivation is to handle guardrails centrally, right now working with Nemo. The issue is: - My tools definition and tool list is with application. I need it to send request with model, provider, other_params and tools_list to gateway for execution. Since tools list is not serializable, this cannot work. This still may not work with Nemo, due to config param issue described elsewhere, but atleast as a framework we can enable remote router functionality along with tools.

Routing just by way of using base_url does help either as gaurdrails do not integrate this way.

Motivation

I have been trying to work with langgraph in a way where model.invoke is separated out into a gateway. Primary motivation is to handle guardrails centrally, right now working with Nemo. The issue is: - My tools definition and tool list is with application. I need it to send request with model, provider, other_params and tools_list to gateway for execution. Since tools list is not serializable, this cannot work. This still may not work with Nemo, due to config param issue described elsewhere, but atleast as a framework we can enable remote router functionality along with tools.

Routing just by way of using base_url does help either as gaurdrails do not integrate this way.

Proposal (If applicable)

Not explored yet.