Clojure is a Lisp-1 and attempts to be a purely functional language (I say attempts because it, of course, isn't pure, but encourages you to write functional code by making the alternatives more complicated). There are some problems this just isn't well suited for, i.e., anything highly stateful. Being able to interface with -- without RPC -- Java or Scala components for that part of your application is a big win.
Finally, because Clojure (and Scala, for that matter) coexist with Java in one runtime, it's possible to incrementally introduce the langage to a legacy Java codebase without needing a "rewrite a doom". I've heard stories of Clojure being introduced to a Java application via, "hey, can I use this library for concurrency called Clojure?".