> For the complete documentation index, see [llms.txt](https://lava-ai.gitbook.io/intelligent-agentic-ecosystem/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lava-ai.gitbook.io/intelligent-agentic-ecosystem/user-tools-cont..md).

# User Tools - Cont.

## Token Intelligence:

*Coin Metadata:*

* Contract address (copyable in alerts).
* Token age.
* Holder count.
* Current price.

*Contract Safety Checks:*

* LP lock verification.
* Ownership renounce status.
* Known rug risk patterns.

*PnL Snapshots:*

* Estimated whale profit/loss per tracked wallet.

## Embedded Trading Actions:

*One Click Trading Integration:*

* Instant Buy and Sell buttons inside alerts.
* Executes trades directly from Telegram 
*  MeV Protection

*⁠Stop Loss / Take Profit Automation:*

* Auto-exit positions when targets are hit. (Phase 2)

*Custom Slippage Control:*

* Basic tier = fixed slippage (5%).
* Pro tier = user-set slippage.

*Personalized Watchlists:*

* Users can add coins or wallets to personal watchlists.
* Alerts filtered only for those assets/wallets.


---

# 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://lava-ai.gitbook.io/intelligent-agentic-ecosystem/user-tools-cont..md?ask=<question>&goal=<endgoal>
```

`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.