Can't zoho.ai.parsePhoneNumber be savvy enough to extrapolate the country from the phone number's country code?

Can't zoho.ai.parsePhoneNumber be savvy enough to extrapolate the country from the phone number's country code?

Ok.  So one of my Deluge scripts involves extrapolating the country name from the country code in the phone number, for which I was going to just create some sort of lookup table.  But... then I came across the zoho.ai.parsePhoneNumber function, and initially thought that this would be perfect. The function is described as follows: 

The zoho.ai.parsePhoneNumber task examines the given phone number to provide its device, network, location, and formatting information.

But then I read a little further where it gives the syntax:

<response> = zoho.ai.parsePhoneNumber(<phone_number>, <country_code>);

Country code?

As Yosemite Sam might say... "I've been horn-swaggled! I've been shim-shammed!"

I mean, color me crazy, but shouldn't an AI-based telephone number slicer/dicer/expresso/functionator be able to, at the very least,  extrapolate the country from the phone number's country code?  Like, isn't that something I'd want the function to figure out for me instead of me having to figure out for the function?

So it does a couple of other neat things, like telling me the time zone based on the phone number, etc.  But... I might suggest that a future incarnation of the function make the country code an optional parameter, in which case if not provided, the function would assume that the country code as being a part of the number, and figure the country based on that.

-Bryan