Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Industry Valuation Distribution

industry_valuation_dist
Read-onlyIdempotent

Fetch the industry PE, PB, and PS valuation distribution for a specified security symbol. Use it to compare a stock's valuation against its sector peers.

Instructions

Get industry PE/PB/PS valuation distribution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional 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.
symbolYesSecurity symbol, e.g. "700.HK". Use the canonical form — a padded code like "00700.HK" returns an empty record, not an error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.0
    • 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: -"Security symbol, e.g. \"700.HK\""New value: +"Security symbol, e.g. \"700.HK\". Use the canonical form — a padded code like \"00700.HK\" returns an empty record, not an error."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "IndustryValuationDistribution": {
-      "properties": {
-        "current_percentile": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "max": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "median": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "min": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "p25": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "p75": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "IndustryValuationDistributions": {
-      "properties": {
-        "pb": {
-          "anyOf": [
-            {
-              "$ref": "#/$defs/IndustryValuationDistribution"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "pe": {
-          "anyOf": [
-            {
-              "$ref": "#/$defs/IndustryValuationDistribution"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "ps": {
-          "anyOf": [
-            {
-              "$ref": "#/$defs/IndustryValuationDistribution"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "distributions": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/IndustryValuationDistributions"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  4. Changed15 schema fields changedv0.6.0
    • removedOutput schema / $defs / IndustryValuationDistribution / description
      Removed value: -"One indicator's distribution stats in `industry_valuation_dist`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / IndustryValuationDistribution / properties / current_percentile / description
      Removed value: -"Where the stock currently sits in this distribution."
    • removedOutput schema / $defs / IndustryValuationDistribution / properties / max / description
      Removed value: -"Maximum value."
    • removedOutput schema / $defs / IndustryValuationDistribution / properties / median / description
      Removed value: -"Median."
    • removedOutput schema / $defs / IndustryValuationDistribution / properties / min / description
      Removed value: -"Minimum value."
    • removedOutput schema / $defs / IndustryValuationDistribution / properties / p25 / description
      Removed value: -"25th percentile."
    • removedOutput schema / $defs / IndustryValuationDistribution / properties / p75 / description
      Removed value: -"75th percentile."
    • removedOutput schema / $defs / IndustryValuationDistributions / description
      Removed value: -"`distributions` block of `industry_valuation_dist`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / IndustryValuationDistributions / properties / pb / description
      Removed value: -"Price-to-book distribution."
    • removedOutput schema / $defs / IndustryValuationDistributions / properties / pe / description
      Removed value: -"Price-to-earnings distribution."
    • removedOutput schema / $defs / IndustryValuationDistributions / properties / ps / description
      Removed value: -"Price-to-sales distribution."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `industry_valuation_dist`. Per-indicator distribution stats\ngrouped under `distributions`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / distributions / description
      Removed value: -"Per-indicator distribution blocks."
    • removedOutput schema / title
      Removed value: -"IndustryValuationDistResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "IndustryValuationDistribution": {
+      "description": "One indicator's distribution stats in `industry_valuation_dist`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "current_percentile": {
+          "description": "Where the stock currently sits in this distribution.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "max": {
+          "description": "Maximum value.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "median": {
+          "description": "Median.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "min": {
+          "description": "Minimum value.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "p25": {
+          "description": "25th percentile.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "p75": {
+          "description": "75th percentile.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "IndustryValuationDistributions": {
+      "description": "`distributions` block of `industry_valuation_dist`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "pb": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/IndustryValuationDistribution"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Price-to-book distribution."
+        },
+        "pe": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/IndustryValuationDistribution"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Price-to-earnings distribution."
+        },
+        "ps": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/IndustryValuationDistribution"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Price-to-sales distribution."
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `industry_valuation_dist`. Per-indicator distribution stats\ngrouped under `distributions`.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "distributions": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/IndustryValuationDistributions"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Per-indicator distribution blocks."
+    }
+  },
+  "title": "IndustryValuationDistResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description does not need to restate safety. It adds mild context by indicating the result concerns PE/PB/PS distribution, but it does not disclose output shape, empty-record behavior, or how the distribution is computed. It does not contradict the 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 a single, front-loaded sentence with no filler or redundant phrasing. It is appropriately compact for a straightforward read-only lookup.

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

Completeness2/5

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

There is no output schema, so the description should explain return semantics, but it only says 'distribution' without describing the shape, scope, or units. It also fails to distinguish this tool from close siblings such as industry_valuation, valuation_rank, and valuation_comparison, leaving a meaningful completeness gap.

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%, with the schema already explaining both _jq and symbol, including the canonical form warning. The description itself adds no parameter-level meaning, so the high-coverage baseline of 3 applies.

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?

The description uses a specific verb and resource: 'Get industry PE/PB/PS valuation distribution.' This is clearer than the bare tool name and conveys the core object of the call. However, it does not explicitly distinguish this tool from closely named siblings like industry_valuation, industry_rank, or valuation_rank.

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?

The description provides no guidance on when to choose this tool over alternatives. It does not state prerequisites, exclusions, or contrast with similar valuation/industry tools. An agent is left to infer usage solely from the name and title.

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

Deploy Server

Other Tools