Asking Lumo to look up stock information

When I ask Lumo to provide information on a stock ticker, it often takes a long time as Lumo has a debate with itself as it works through the question.

The root cause is straightforward: the reasoning model attempted internal validation before tool execution. It checked "SKHY" against training-data knowledge, didn't recognize it, then spent cognitive cycles generating alternative hypotheses (SCHD, SKYY, SHY) before finally deciding to just try the tool.

The tool is the validator. The deliberation was unnecessary overhead.

Why it happens:

The model's default behavior is to assess whether a request is "reasonable" before acting. For ticker symbols it doesn't recognize from training data, it enters a pattern-match loop:

1. Is this a known ticker? → No match in training data
2. What could it be a typo for? → Generates candidates
3. Should I ask for clarification or just try? → Debates
4. Eventually tries the tool → Gets valid data back

This is worse for niche tickers (foreign ADRs, lesser-known ETFs) because they're underrepresented in training data. SCHD would have triggered zero deliberation.

How to remediate it:

In your behavior configuration, add a directive:

This eliminates the pre-flight reasoning loop. The model goes straight to stock(symbol=X) and handles the result—success or failure—afterward.

Why this works: It reframes the tool as a lookup function rather than a downstream verifier. The model skips the "do I believe this ticker exists?" step entirely and treats the API response as ground truth.

One caveat: This won't eliminate all latency. The stock tool itself takes time to return data. But it will remove the 5-10 seconds of visible reasoning spent on internal ticker validation.

**NOTE- I have created a Project for Financial Matters and I put the text the "Instructions" section so that tokens and attention are not consumed when I am having other types of chats