longbridge

Official

by longbridge

Overview Schema Source Related Servers Score Discussions(1)Admin

Rust

Hybrid

Short Trades

short_trades

Read-onlyIdempotent

Retrieve daily short-sale volume history for US or HK stocks. Market is inferred from the symbol suffix, with data sourced from FINRA/NASDAQ for US and HKEX for Hong Kong.

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
`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)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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

A4.5/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool's safety profile is clear. The description adds valuable behavioral context beyond annotations, such as market inference logic, data sources (FINRA/NASDAQ, HKEX), and parameter semantics (e.g., last_timestamp as unix seconds). No contradiction with annotations.

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?

The description is extremely concise at four sentences, front-loading the core purpose ('Get daily short-sale volume history for HK or US stocks') and then immediately covering key behavioral and parameter details without any superfluous content.

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

Completeness5/5

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

Given the presence of an output schema (documenting return values) and comprehensive annotations, the description covers all necessary behavioral and usage context: market scope, symbol inference, parameter details, and data sources. It is fully adequate for an agent to correctly invoke this tool.

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

Parameters4/5

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

Schema coverage is 100%, so the schema documents parameters well. The description adds further meaning by explaining that last_timestamp is in unix seconds and can be omitted for latest data, page_size range (1-100) and default (20), and provides a symbol example with suffixes. This enhances the schema's documentation.

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 clearly states the tool retrieves 'daily short-sale volume history' for a specific set of markets (HK or US), with a specific resource (short-sale volume) and scope (HK/US), and distinguishes from siblings by focusing on short-sale volume data as opposed to related tools like short_margin or short_positions.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool (get short-sale volume history for HK/US stocks), explains market inference from symbol suffix, and mentions data sources. However, it does not explicitly state when not to use this tool or provide alternatives among siblings, which would be helpful given the many related tools.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

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