> For the complete documentation index, see [llms.txt](https://support.tiger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.tiger.com/english/tables/signals.md).
# Signals
This window displays all signals triggered by the parameters specified in the terminal in text form.
Displaying Signals in the Tiger.com terminal
The window contains:
* **Sources** — signals from the **Chart** window or signals from the **Trade feed** window can be selected as a source separately or together.
* **Clear** — the button clears fields with passed signals.
| Column | Description |
| ------- | --------------------------------------------------------------------- |
| Time | Indicates the time when the event took place. |
| Source | Indicates the source where the event took place. |
| Symbol | Indicates the ticker of the instrument with which the event occurred. |
| Message | Briefly describes the event that took place. |
---
# 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://support.tiger.com/english/tables/signals.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.
