Feature Request: Return informational message instead of 0 when querying non-existent collection in `list-collections`

[ryanbradley]

When a non-existent collection or database is queried, the server returns 0. Instead, the server could return an informational message that the queried collection / database does not exist.

[github-actions]

Thanks for opening this issue. The ticket MCP-431 was created for internal tracking.

[gagik]

The problem here is that a database with 0 collections and a database that "doesn't exist" is essentially the same thing.
In a sense it would misleading to say that it doesn't exist because there's no need to create the database, one can switch to any arbitrary database name and create a collection in it.

Is this causing any issues for your workflow?