Is it possible to query for a Drive object without having the Site ID available, only its "connection string"?

[uxmal]

I have working code right now that obtains a Drive instance (in fact it's a SharePoint document library in case that makes any difference. The code looks like this:

            var site = await client
               .Sites["mytenancy.sharepoint.com:/sites/MySite"]
               .Request()
               .GetAsync();

            var docLibs = await client
                .Sites[site.Id]
                .Drives
                .Request()
                //.Filter($"name eq 'MyDocLib'")        // BUG? doesn't filter
                .GetAsync();

I don't have the Graph ID's for the site or the document library "ahead of time"; all I have is the "connection string" and the doc library name. As mentioned the code works (except that the Filter operation doesn't appear to have any effect, so I do a manual LinQ .Where(d => d.Name == "MyDocLib") after the fact).

The two network I/Os bother me. I'd like to do everything in one network I/O. It seems logical that you should be able to do the following:

            var site = await client
                .Sites["mytenancy.sharepoint.com:/sites/MySite"]
                .Drives
                .Request()
                //.Filter($"name eq 'MyDocLib'")        // BUG? doesn't filter
                .GetAsync();

but when I try executing this I get a variation of "bad url" in an exception.

Is there a way to avoid that second network I/O based on only the "connection string" and the document library name? I have nowhere to store the Graph site ID and document library name in my application at the moment, so I can't cache those values from one request to another.