Non-invasive tracing
Lisp environments generally provide interactive debugging environment and trace mechanisms. For example, in SBCL, you could use the trace macro: you don't even need to modify your code, like you did in your Java example.
For Clojure, look at the tools.trace library, or the following answer: clojure: adding a debug trace to every function in a namespace?
Custom functions and macros
See also the many answers to this question: Debugging in Clojure? Most of them involve nesting the expression you want to debug/trace inside another expression, like Chiron suggested.
I don't think that "I have to reformat and close the brackets appropriately" is a good argument; everytime you edit your program you have to deal with the syntax, or else you won't ever modify your code.
Paredit
I personally don't use I am now a happy user of Paredit. Your editor keep track of parens and brackets while you code, which is quite handy.
Reader macros
I you really don't want to nest your expression inside another one, I suppose you could write a reader macro so that you could annotate an expression with a debug statement, but this is overkill, imho (edit: this is what spyscope does, apparently; see NielsK's answer).