Skip to main content
Glama
longbridge

longbridge

Official

Industry Peers

industry_peers
Read-onlyIdempotent

Drill into an industry group's sub-sector tree using its BK counter_id to see stock counts, daily changes, and YTD changes per node.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesBK counter_id from `industry_rank`, e.g. "BK/US/IN00258".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNo
chainNo

Schema Changelog

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

  1. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"IndustryPeersParam"
  2. Changed15 schema fields changedv0.6.0
    • 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"
  3. Changed1 schema field changedv0.5.6
    • 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"
      +}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. Addedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

Beyond readOnlyHint and idempotentHint annotations, the description discloses the tree structure and data shown per node (stock count, daily change, YTD change), adding useful behavioral context.

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, no fluff; front-loaded with purpose immediately, followed by input and output details.

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 simple single-parameter tool, output schema exists, and annotations provide safety profile, the description is sufficiently complete.

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?

The schema already describes the symbol parameter, but the description adds the origin (from industry_rank) and an example format, enhancing understanding.

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?

Clearly states it provides a hierarchical sub-sector tree for an industry group. Specific verb+resource, but does not explicitly distinguish from sibling tools 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 Guidelines3/5

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

Indicates the input comes from industry_rank, implying a prerequisite, but does not provide explicit when-to-use or alternatives.

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

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