longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Security List

security_list

Read-onlyIdempotent

Fetch paginated security lists for US, HK, CN, and SG markets, with optional Overnight category filter.

Instructions

Get security list for a market. Supports market: US, HK, CN, SG. category: "Overnight" (default). page: 1-based page number (default 1). count: records per page (default 50).

Input Schema

TableJSON Schema

Name	Required	Description
`_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.
`page`	No	Page number, 1-based (default: 1)
`count`	No	Records per page (default: 50)
`market`	Yes	Market code: US, HK, CN, SG
`category`	No	Category filter. Currently only "Overnight" is supported; omitting defaults to Overnight.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields 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."

removedInput schema / properties / count / format
```
Removed value: -"uint"
```
removedInput schema / properties / page / format
```
Removed value: -"uint"
```

Changed2 schema fields changedv0.10.6Sep 10, 2026

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

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "SecurityListItem": {
-      "properties": {
-        "name_cn": {
-          "type": "string"
-        },
-        "name_en": {
-          "type": "string"
-        },
-        "name_hk": {
-          "type": "string"
-        },
-        "symbol": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "symbol",
-        "name_cn",
-        "name_en",
-        "name_hk"
-      ],
-      "type": "object"
-    }
-  },
-  "properties": {
-    "count": {
-      "format": "uint",
-      "minimum": 0,
-      "type": "integer"
-    },
-    "items": {
-      "items": {
-        "$ref": "#/$defs/SecurityListItem"
-      },
-      "type": "array"
-    },
-    "page": {
-      "format": "uint",
-      "minimum": 0,
-      "type": "integer"
-    },
-    "total": {
-      "format": "uint",
-      "minimum": 0,
-      "type": "integer"
-    }
-  },
-  "required": [
-    "total",
-    "page",
-    "count",
-    "items"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"SecurityListParam"
```

Changed11 schema fields changedv0.6.0Jun 26, 2026

removedOutput schema / $defs / SecurityListItem / properties / name_cn / description
```
Removed value: -"Security name (zh-CN)."
```
removedOutput schema / $defs / SecurityListItem / properties / name_en / description
```
Removed value: -"Security name (en)."
```
removedOutput schema / $defs / SecurityListItem / properties / name_hk / description
```
Removed value: -"Security name (zh-HK)."
```
removedOutput schema / $defs / SecurityListItem / properties / symbol / description
```
Removed value: -"Security symbol, e.g. \"AAPL.US\"."
```

removedOutput schema / $schema

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

removedOutput schema / description

Removed value: -"Returned by `security_list`. Top-level pagination envelope built in\n`quote::security_list` around the upstream `Vec<Security>`."

removedOutput schema / properties / count / description

Removed value: -"Records-per-page echoed back from the request."

removedOutput schema / properties / items / description
```
Removed value: -"The securities on this page."
```

removedOutput schema / properties / page / description

Removed value: -"1-based page number echoed back from the request."

removedOutput schema / properties / total / description

Removed value: -"Total number of securities available for this market/category (before\npagination)."

removedOutput schema / title
```
Removed value: -"SecurityListResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "SecurityListItem": {
+      "properties": {
+        "name_cn": {
+          "description": "Security name (zh-CN).",
+          "type": "string"
+        },
+        "name_en": {
+          "description": "Security name (en).",
+          "type": "string"
+        },
+        "name_hk": {
+          "description": "Security name (zh-HK).",
+          "type": "string"
+        },
+        "symbol": {
+          "description": "Security symbol, e.g. \"AAPL.US\".",
+          "type": "string"
+        }
+      },
+      "required": [
+        "symbol",
+        "name_cn",
+        "name_en",
+        "name_hk"
+      ],
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `security_list`. Top-level pagination envelope built in\n`quote::security_list` around the upstream `Vec<Security>`.",
+  "properties": {
+    "count": {
+      "description": "Records-per-page echoed back from the request.",
+      "format": "uint",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "items": {
+      "description": "The securities on this page.",
+      "items": {
+        "$ref": "#/$defs/SecurityListItem"
+      },
+      "type": "array"
+    },
+    "page": {
+      "description": "1-based page number echoed back from the request.",
+      "format": "uint",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "total": {
+      "description": "Total number of securities available for this market/category (before\npagination).",
+      "format": "uint",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "page",
+    "count",
+    "items"
+  ],
+  "title": "SecurityListResponse",
+  "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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds default values for category, page, and count, which is useful behavioral context, but does not disclose behavior for invalid inputs or pagination details beyond defaults.

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

Conciseness5/5

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

One sentence with all key details (market, category, page, count) front-loaded. No redundancy or fluff.

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

Completeness4/5

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

For a simple read-only list tool with no output schema, the description covers the main parameters and defaults adequately. It could mention response structure or error behavior, but the essentials are present.

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?

Schema description coverage is 100% and includes defaults and allowed values for each parameter. The description repeats these details without adding new meaning, so it meets the baseline but does not exceed it.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States 'Get security list for a market' with specific supported markets and category options. Clearly a distinct resource from siblings like sharelist_list, and the scope is well-defined.

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?

Provides no guidance on when to use this tool versus alternatives such as sharelist_list or watchlist. No exclusions or conditions are mentioned, leaving selection to inference.

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

Deploy Server

Security List

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools