Unfortunately not - the problem is we can't "know" what your expression is without parsing it...and we can't parse it without having the "context" of an actual alarm to evaluate within...and if we faked an alarm context, then you might get unexpected values on the evaluation. It's a real chicken and egg problem.
Someone else tried to do pretty much what you're trying to do and documented their efforts here:
And created a feature request: