alert_listRetrieve all configured price alerts in one view. Use this to review active alerts across US and HK markets and manage your monitoring strategy.
Get all configured price alerts.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| lists | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.6.0Output schema / $defs / AlertIndicator / descriptionRemoved value: -"A single configured price-alert indicator."Output schema / $defs / AlertIndicator / properties / condition / descriptionRemoved value: -"Alert condition."Output schema / $defs / AlertIndicator / properties / enabled / descriptionRemoved value: -"Whether the alert is currently enabled."Output schema / $defs / AlertIndicator / properties / frequency / descriptionRemoved value: -"Alert frequency."Output schema / $defs / AlertIndicator / properties / id / descriptionRemoved value: -"Alert (indicator) ID. Use as `alert_id` in alert_delete/enable/disable."Output schema / $defs / AlertIndicator / properties / indicator_id / descriptionRemoved value: -"Indicator type ID."Output schema / $defs / AlertIndicator / properties / price / descriptionRemoved value: -"Threshold price or percentage value."Output schema / $defs / AlertIndicator / properties / triggered_at / descriptionRemoved value: -"Time the alert last triggered (RFC3339), if any."Output schema / $defs / AlertSymbolGroup / descriptionRemoved value: -"A group of alert indicators configured for one security."Output schema / $defs / AlertSymbolGroup / properties / indicators / descriptionRemoved value: -"Configured alert indicators for this symbol."Output schema / $defs / AlertSymbolGroup / properties / symbol / descriptionRemoved value: -"Security symbol (upstream `counter_id`, normalized to `<CODE>.<MARKET>`)."Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Output schema / descriptionRemoved value: -"Returned by `alert_list`. The upstream price-alert payload, forwarded after\nthe standard transform (note: upstream `counter_id` is renamed to `symbol`\nand `*_at` timestamps become RFC3339). Subset of the wire payload — only the\ndocumented fields are declared; all are optional."Output schema / properties / lists / descriptionRemoved value: -"Per-symbol alert groups."Output schema / titleRemoved value: -"AlertListResponse"v0.5.6Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "AlertIndicator": {
+ "description": "A single configured price-alert indicator.",
+ "properties": {
+ "condition": {
+ "description": "Alert condition.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "enabled": {
+ "description": "Whether the alert is currently enabled.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "frequency": {
+ "description": "Alert frequency.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "id": {
+ "description": "Alert (indicator) ID. Use as `alert_id` in alert_delete/enable/disable.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "indicator_id": {
+ "description": "Indicator type ID.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "price": {
+ "description": "Threshold price or percentage value.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "triggered_at": {
+ "description": "Time the alert last triggered (RFC3339), if any.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "AlertSymbolGroup": {
+ "description": "A group of alert indicators configured for one security.",
+ "properties": {
+ "indicators": {
+ "description": "Configured alert indicators for this symbol.",
+ "items": {
+ "$ref": "#/$defs/AlertIndicator"
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+ },
+ "symbol": {
+ "description": "Security symbol (upstream `counter_id`, normalized to `<CODE>.<MARKET>`).",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ }
+ },
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "description": "Returned by `alert_list`. The upstream price-alert payload, forwarded after\nthe standard transform (note: upstream `counter_id` is renamed to `symbol`\nand `*_at` timestamps become RFC3339). Subset of the wire payload — only the\ndocumented fields are declared; all are optional.",
+ "properties": {
+ "lists": {
+ "description": "Per-symbol alert groups.",
+ "items": {
+ "$ref": "#/$defs/AlertSymbolGroup"
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+ }
+ },
+ "title": "AlertListResponse",
+ "type": "object"
+}v0.4.5v0.4.0v0.3.2v0.3.1v0.1.12Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description adds no extra behavioral context. It does not contradict the annotations, but it also does not elaborate on traits like empty list behavior or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no extraneous information. It is front-loaded and efficiently conveys the tool's function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with no parameters and an output schema present. The description is sufficient for basic understanding, though it could mention that the output is a list of alert objects. Given the output schema, this is a minor gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and schema coverage is 100%. Per guidelines, baseline is 4. The description adds no parameter details, which is acceptable given no parameters exist.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and the resource 'all configured price alerts', making the tool's purpose unambiguous. It differentiates from sibling tools like alert_add and alert_delete.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, such as when to list versus add or delete alerts. No context about appropriate situations or exclusions is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/longbridge/longbridge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server