> For the complete documentation index, see [llms.txt](https://bhagavata.keshavaswami.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bhagavata.keshavaswami.com/canto-09/d.r.a.g/d-durvasa-and-ambarish-1-5/power-and-purity/character.md). # Character In the Ramayana, we hear of how Lord Rama would enlist spies to gather information on how the citizens were feeling about the king and his ruling. When such information would come back, He would use that feedback to refine His character and approach. This is a far cry from modern politics where spin doctors and public relations tycoons are employed to generate false propaganda and cover up any faults that may be there. Saintly kings lived with high principles, thus inspiring all the citizens to do the same. Their spotless integrity generated so much faith in their followers that there was no question of revolution or revolt. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://bhagavata.keshavaswami.com/canto-09/d.r.a.g/d-durvasa-and-ambarish-1-5/power-and-purity/character.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.