longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Industry Peers

industry_peers

Read-onlyIdempotent

Retrieve a hierarchical sub-sector tree for an industry group. Each node displays stock count, daily change, and YTD change using an industry symbol from industry_rank.

Instructions

Hierarchical sub-sector tree for an industry group. Accepts an industry symbol from industry_rank (e.g. IN00258.US). Each node shows stock count, daily change, and YTD change.

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.
`symbol`	Yes	Industry symbol from `industry_rank`, e.g. "IN00258.US". The BK counter_id form ("BK/US/IN00258") is also accepted.

Schema Changelog

Changes observed during successful MCP inspections.

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

changedInput schema / properties / symbol / description

Previous value: -"BK counter_id from `industry_rank`, e.g. \"BK/US/IN00258\"."New value: +"Industry symbol from `industry_rank`, e.g. \"IN00258.US\". The BK\ncounter_id form (\"BK/US/IN00258\") is also accepted."

Changed2 schema fields changedv0.10.6Sep 10, 2026

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

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "IndustryPeersNode": {
-      "properties": {
-        "chg": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "counter_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "next": {
-          "items": {
-            "$ref": "#/$defs/IndustryPeersNode"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        },
-        "stock_num": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "ytd_chg": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "IndustryPeersTop": {
-      "properties": {
-        "market": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "chain": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/IndustryPeersNode"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "top": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/IndustryPeersTop"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"IndustryPeersParam"
```
Changed15 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / IndustryPeersNode / description
```
Removed value: -"One node in `industry_peers`' `chain` tree. Self-referential via `next`.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / $defs / IndustryPeersNode / properties / chg / description
```
Removed value: -"Daily change."
```
- removedOutput schema / $defs / IndustryPeersNode / properties / counter_id / description
```
Removed value: -"Node identifier (transformed from `counter_id`)."
```
- removedOutput schema / $defs / IndustryPeersNode / properties / name / description
```
Removed value: -"Node name."
```
- removedOutput schema / $defs / IndustryPeersNode / properties / next / description
```
Removed value: -"Child sub-sector nodes."
```
- removedOutput schema / $defs / IndustryPeersNode / properties / stock_num / description
```
Removed value: -"Number of stocks in this sub-sector."
```
- removedOutput schema / $defs / IndustryPeersNode / properties / ytd_chg / description
```
Removed value: -"Year-to-date change."
```
- removedOutput schema / $defs / IndustryPeersTop / description
```
Removed value: -"`top` block of `industry_peers`.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / $defs / IndustryPeersTop / properties / market / description
```
Removed value: -"Market code."
```
- removedOutput schema / $defs / IndustryPeersTop / properties / name / description
```
Removed value: -"Industry group name."
```
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / description
```
Removed value: -"Returned by `industry_peers`. A hierarchical sub-sector tree (`chain`) plus\nthe originating industry group (`top`).\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / properties / chain / description
```
Removed value: -"Root node of the sub-sector tree."
```
- removedOutput schema / properties / top / description
```
Removed value: -"The originating industry group."
```
- removedOutput schema / title
```
Removed value: -"IndustryPeersResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "IndustryPeersNode": {
+      "description": "One node in `industry_peers`' `chain` tree. Self-referential via `next`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "chg": {
+          "description": "Daily change.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "counter_id": {
+          "description": "Node identifier (transformed from `counter_id`).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Node name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "next": {
+          "description": "Child sub-sector nodes.",
+          "items": {
+            "$ref": "#/$defs/IndustryPeersNode"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "stock_num": {
+          "description": "Number of stocks in this sub-sector.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "ytd_chg": {
+          "description": "Year-to-date change.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "IndustryPeersTop": {
+      "description": "`top` block of `industry_peers`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "market": {
+          "description": "Market code.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Industry group name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `industry_peers`. A hierarchical sub-sector tree (`chain`) plus\nthe originating industry group (`top`).\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "chain": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/IndustryPeersNode"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Root node of the sub-sector tree."
+    },
+    "top": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/IndustryPeersTop"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The originating industry group."
+    }
+  },
+  "title": "IndustryPeersResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
Addedv0.3.0May 15, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds useful output details (node contents: stock count, daily change, YTD change) but does not disclose potential size limits, hierarchy depth, or response shape.

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?

Two sentences with no filler. The first sentence states the core purpose, and the second provides the input format and output fields. Front-loaded and efficient.

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 lookup with one required parameter, the description covers the input, output fields, and relationship to industry_rank. Without an output schema, it gives enough for an agent to call and interpret the result.

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 coverage is 100%; the symbol parameter already includes format examples and the alternate BK form. The description repeats the industry_rank provenance but adds no new parameter-level meaning. Baseline 3 is appropriate.

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 resource ('hierarchical sub-sector tree for an industry group'), the required input type (industry symbol), and what each node shows. This clearly distinguishes it from related siblings like industry_rank or industry_valuation.

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?

It explicitly says the tool accepts a symbol from industry_rank, which implies a usage workflow and prerequisite. It does not name alternatives or exclusions, but the context is clear enough for selecting this tool over ranking or valuation siblings.

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

Deploy Server

Industry Peers

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools