longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Short Trades

short_trades

Read-onlyIdempotent

Get daily short-sale volume history for US or HK stocks. Pass the symbol and timestamp cutoff to fetch FINRA/NASDAQ or HKEX daily short-selling data.

Instructions

Get daily short-sale volume history for HK or US stocks. Market inferred from symbol suffix. last_timestamp: unix seconds (omit for latest). page_size: 1–100 (default 20). US source: FINRA/NASDAQ daily. HK source: HKEX daily.

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.
`symbol`	Yes	Security symbol, e.g. "AAPL.US" (US) or "700.HK" (HK). Market is inferred from suffix.
`page_size`	No	Page size: 1–100 (default: 20)
`last_timestamp`	Yes	Query cutoff timestamp in seconds (pass current timestamp for latest data)

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": {
-    "ShortTradesItem": {
-      "properties": {
-        "balance": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "close": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "market_vol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "nasdaq_vol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "nyse_vol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "rate": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "short_vol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "timestamp": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "data": {
-      "items": {
-        "$ref": "#/$defs/ShortTradesItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

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

Changed12 schema fields changedv0.6.0Jun 26, 2026

removedOutput schema / $defs / ShortTradesItem / properties / balance / description
```
Removed value: -"HK only — outstanding short balance (HKD)."
```
removedOutput schema / $defs / ShortTradesItem / properties / close / description
```
Removed value: -"Close price for the day."
```
removedOutput schema / $defs / ShortTradesItem / properties / market_vol / description
```
Removed value: -"HK only — total market trading volume for the day."
```
removedOutput schema / $defs / ShortTradesItem / properties / nasdaq_vol / description
```
Removed value: -"US only — NASDAQ short volume."
```
removedOutput schema / $defs / ShortTradesItem / properties / nyse_vol / description
```
Removed value: -"US only — NYSE short volume."
```

removedOutput schema / $defs / ShortTradesItem / properties / rate / description

Removed value: -"Short volume as a ratio of total volume (decimal, e.g. 0.36 = 36%)."

removedOutput schema / $defs / ShortTradesItem / properties / short_vol / description
```
Removed value: -"Daily short-sale volume in shares."
```
removedOutput schema / $defs / ShortTradesItem / properties / timestamp / description
```
Removed value: -"Trade date (RFC3339)."
```

removedOutput schema / $schema

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

removedOutput schema / description

Removed value: -"Returned by `short_trades`. Wraps a unified `data` array of daily short-sale\nvolume history for HK or US stocks. Market-specific fields are populated\nonly for their respective market (US: `nasdaq_vol`/`nyse_vol`; HK:\n`balance`/`market_vol`). Subset of the wire response."

removedOutput schema / properties / data / description
```
Removed value: -"Daily short-sale volume entries."
```
removedOutput schema / title
```
Removed value: -"ShortTradesResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ShortTradesItem": {
+      "properties": {
+        "balance": {
+          "description": "HK only — outstanding short balance (HKD).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "close": {
+          "description": "Close price for the day.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "market_vol": {
+          "description": "HK only — total market trading volume for the day.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "nasdaq_vol": {
+          "description": "US only — NASDAQ short volume.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "nyse_vol": {
+          "description": "US only — NYSE short volume.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "rate": {
+          "description": "Short volume as a ratio of total volume (decimal, e.g. 0.36 = 36%).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "short_vol": {
+          "description": "Daily short-sale volume in shares.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "timestamp": {
+          "description": "Trade date (RFC3339).",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `short_trades`. Wraps a unified `data` array of daily short-sale\nvolume history for HK or US stocks. Market-specific fields are populated\nonly for their respective market (US: `nasdaq_vol`/`nyse_vol`; HK:\n`balance`/`market_vol`). Subset of the wire response.",
+  "properties": {
+    "data": {
+      "description": "Daily short-sale volume entries.",
+      "items": {
+        "$ref": "#/$defs/ShortTradesItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "ShortTradesResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context: data sources for US (FINRA/NASDAQ) and HK (HKEX), market inference, and pagination limits. It does not mention return format, but the annotation coverage lowers that burden.

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?

Four short sentences, each serving a distinct purpose: what the tool does, market inference, timestamp semantics, page size, and data sources. No filler; the primary verb and resource are front-loaded. The information density is appropriate without being bloated.

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 read-only data-query tool with fully documented parameters and safety annotations, the description covers essential context: data sources, market inference, pagination defaults, and timestamp behavior. The only notable omission is the exact return structure, but the semantic of 'volume history' plus the lack of an output schema make this acceptable.

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

Parameters2/5

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

Schema coverage is 100%, so baseline is 3, but the description introduces a contradiction: 'last_timestamp: unix seconds (omit for latest)' conflicts with the schema's required flag for last_timestamp. This actively misleads invocation. The page_size range matches the schema and adds little beyond 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?

The description states a specific verb ('Get'), a specific resource ('daily short-sale volume history'), and the market scope ('HK or US stocks'). It also notes the market is inferred from the symbol suffix, clarifying behavior. This is clearly distinguishable from sibling tools like short_positions or short_margin, which address different data types.

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

Usage Guidelines3/5

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

The description gives clear context for when to use the tool (when short-sale volume history is needed) and helpful usage tips (last_timestamp semantics, page_size range). However, it does not explicitly name alternative sibling tools or state when not to use this tool, so there are no exclusions.

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

Deploy Server

Short Trades

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools