Different configTool on every API request

Gemini API
,
1

Can configTool be defined in a subsequent API call, not to override the configTool defined in cached content?

I am going to use a list of functions, and I need the model to be limited to only a subset of functions. I also want to use cachedContent and include the function schema on cached content. But every request is going to have totally different `allowedFunctionNames`, which is a property in `configTool`.

From my experience, it seems like when I define toolConfig to make a request by `sendMessageStream`, it overrides the default config defined altogether and loses access to function calls.

2

Maybe I made the question too complicated earlier.
Here’s the short version:

Is allowedFunctionNames in configTool considered part of the prompt that’s applied earlier or later in the prompt sequence?

This matters because if allowedFunctionNames is appended after the cached content, then we can efficiently use cached content for the full tool schema and dynamically restrict function access per request.