longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

List Price Alerts

alert_list

Read-onlyIdempotent

Retrieve all configured price alerts for US and HK markets. Optionally filter the JSON response with a jq query to extract specific fields.

Instructions

Get all configured price alerts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`_jq`	No	Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data \| map({symbol}). Omit for the full response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.12.0Sep 23, 2026

addedInput schema / properties / _jq / description

Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."

Changed2 schema fields changedv0.10.6Sep 10, 2026

addedInput schema / properties / _jq
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "AlertIndicator": {
-      "properties": {
-        "condition": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "enabled": {
-          "type": [
-            "boolean",
-            "null"
-          ]
-        },
-        "frequency": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "indicator_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "price": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "triggered_at": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "AlertSymbolGroup": {
-      "properties": {
-        "indicators": {
-          "items": {
-            "$ref": "#/$defs/AlertIndicator"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        },
-        "symbol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "lists": {
-      "items": {
-        "$ref": "#/$defs/AlertSymbolGroup"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed15 schema fields changedv0.6.0Jun 26, 2026

removedOutput schema / $defs / AlertIndicator / description

Removed value: -"A single configured price-alert indicator."

removedOutput schema / $defs / AlertIndicator / properties / condition / description
```
Removed value: -"Alert condition."
```
removedOutput schema / $defs / AlertIndicator / properties / enabled / description
```
Removed value: -"Whether the alert is currently enabled."
```
removedOutput schema / $defs / AlertIndicator / properties / frequency / description
```
Removed value: -"Alert frequency."
```

removedOutput schema / $defs / AlertIndicator / properties / id / description

Removed value: -"Alert (indicator) ID. Use as `alert_id` in alert_delete/enable/disable."

removedOutput schema / $defs / AlertIndicator / properties / indicator_id / description
```
Removed value: -"Indicator type ID."
```
removedOutput schema / $defs / AlertIndicator / properties / price / description
```
Removed value: -"Threshold price or percentage value."
```
removedOutput schema / $defs / AlertIndicator / properties / triggered_at / description
```
Removed value: -"Time the alert last triggered (RFC3339), if any."
```

removedOutput schema / $defs / AlertSymbolGroup / description

Removed value: -"A group of alert indicators configured for one security."

removedOutput schema / $defs / AlertSymbolGroup / properties / indicators / description
```
Removed value: -"Configured alert indicators for this symbol."
```

removedOutput schema / $defs / AlertSymbolGroup / properties / symbol / description

Removed value: -"Security symbol (upstream `counter_id`, normalized to `<CODE>.<MARKET>`)."

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / description

Removed 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."

removedOutput schema / properties / lists / description
```
Removed value: -"Per-symbol alert groups."
```
removedOutput schema / title
```
Removed value: -"AlertListResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput 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"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
First observedv0.1.12May 8, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds no extra behavioral context beyond the basic retrieval statement—no mention of return format, ordering, pagination, or whether disabled alerts are included. With annotations covering safety, the description still adds little value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that conveys the core purpose without waste. It is appropriately sized for a simple list operation, though it could include more context without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one optional parameter and no output schema, the description is minimal but adequate. However, it lacks any details about the response (e.g., whether it returns an array, includes disabled alerts, or any default behavior). Given the sibling tools, mentioning that it returns all alerts regardless of state could be helpful, but it is not critical for a straightforward list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter is the optional _jq filter, which is fully documented in the schema (100% coverage). The description does not need to explain it, as the schema handles it. The baseline of 3 is appropriate since the schema carries the parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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 purpose unambiguous. It distinguishes from sibling alert management tools (add/delete/enable/disable) by implying a listing operation, but does not explicitly name them. The name 'alert_list' reinforces this, so it is clear enough for an agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus the many alert-related siblings (alert_add, alert_disable, etc.). The description does not mention any context, exclusions, or alternatives. An agent must infer that this is for retrieval, not modification.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

List Price Alerts

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools