◇ Could this help me?
Yes for the architecture, with the trend claims set aside. Consolidating into one structured store and pointing the assistant at that is sound and matches what people who do this seriously end up with: a question answered by fanning out across many tools is slow, expensive, and unreliable, while the same question against one structured store is a query. Structured storage also beats similarity search for anything you can name, which is most business data. General practice, with two honest corrections: search interest in a technology is not evidence that anyone is removing anything, so treat the opening trend claim as rhetoric, and a single store containing everything is a concentration of access that deserves more thought about permissions than a scattering of narrow connectors did.
I want to stop answering questions by fanning out across a dozen connected tools. For the data sources I describe below, help me design one consolidated structured store instead: what tables it needs, what the key is for each, how often each source syncs, and what gets dropped rather than copied. Then tell me what the single most common question I ask would look like as a query against that store rather than as a set of tool calls. Finally, be direct about the downside: this store would hold everything in one readable place, so tell me what access controls it needs and what the consequence would be if the wrong thing could read it.