> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/investing/momentum-and-oscillators/mean-reversion-oscillator/features.md). # Features Mean Reversion Oscillator Features The **Mean Reversion Oscillator (MRO)** is designed to be simple yet powerful, giving traders a clear view of how far price has stretched away from its mean. Its features focus on clarity, adaptability, and integration with other trading tools. * πŸ“Š **Bounded Scale (0–100):** Normalizes price deviations into an easy-to-read range. * βš–οΈ **Configurable Inputs:** Flexible control over MA Length and StdDev Length to match different trading styles (scalping, swing, long-term). * 🎨 **Dynamic Visuals:** Color-coded signals (red, green, blue) and background shading for instant recognition of extremes. * βž– **Reference Levels:** Built-in Overbought, Oversold, and Midline markers to guide interpretation. * πŸ”Ž **Divergence Detection (manual):** When price forms new highs/lows but MRO doesn’t, it can reveal hidden momentum shifts. * πŸͺΆ **Lightweight Implementation:** Optimized script runs smoothly, even with multiple indicators on chart. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.candelacharts.com/investing/momentum-and-oscillators/mean-reversion-oscillator/features.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.