The command to check the sharding metadata consistency, i.e., checkMetadataConsistency, returns a list of malformed entries when it runs with the granularity of cluster-level.

Specifically, it seems that this test causes a metadata inconsistency, but the entry returned by the command is actually the string "0" (double-quote included) instead of a JSON containing detailed information on the detected inconsistency.