Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Industry Valuation

industry_valuation
Read-onlyIdempotent

Compare a stock's valuation against its industry peers by entering a security symbol. Retrieve key metrics to assess relative value for investment decisions.

Instructions

Get industry valuation comparison for peers.

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": {
-    "IndustryValuationHistoryPoint": {
-      "properties": {
-        "date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "pb": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "pe": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "IndustryValuationItem": {
-      "properties": {
-        "dividend_yield": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "history": {
-          "items": {
-            "$ref": "#/$defs/IndustryValuationHistoryPoint"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "pb": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "pe": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "ps": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "symbol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "list": {
-      "items": {
-        "$ref": "#/$defs/IndustryValuationItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  4. Changed16 schema fields changedv0.6.0
    • removedOutput schema / $defs / IndustryValuationHistoryPoint / description
      Removed value: -"One history point in `industry_valuation`'s nested `history`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / IndustryValuationHistoryPoint / properties / date / description
      Removed value: -"Sample date (RFC3339; rewritten from a unix-epoch field)."
    • removedOutput schema / $defs / IndustryValuationHistoryPoint / properties / pb / description
      Removed value: -"Price-to-book at this date."
    • removedOutput schema / $defs / IndustryValuationHistoryPoint / properties / pe / description
      Removed value: -"Price-to-earnings at this date."
    • removedOutput schema / $defs / IndustryValuationItem / description
      Removed value: -"One peer in `industry_valuation`'s `list`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / IndustryValuationItem / properties / dividend_yield / description
      Removed value: -"Dividend yield."
    • removedOutput schema / $defs / IndustryValuationItem / properties / history / description
      Removed value: -"Per-date history of PE/PB."
    • removedOutput schema / $defs / IndustryValuationItem / properties / name / description
      Removed value: -"Display name."
    • removedOutput schema / $defs / IndustryValuationItem / properties / pb / description
      Removed value: -"Price-to-book."
    • removedOutput schema / $defs / IndustryValuationItem / properties / pe / description
      Removed value: -"Price-to-earnings."
    • removedOutput schema / $defs / IndustryValuationItem / properties / ps / description
      Removed value: -"Price-to-sales."
    • removedOutput schema / $defs / IndustryValuationItem / properties / symbol / description
      Removed value: -"Security symbol (transformed from `counter_id`)."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `industry_valuation`. Wraps a `list` of industry peers.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / list / description
      Removed value: -"Peers in the same industry."
    • removedOutput schema / title
      Removed value: -"IndustryValuationResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "IndustryValuationHistoryPoint": {
+      "description": "One history point in `industry_valuation`'s nested `history`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "date": {
+          "description": "Sample date (RFC3339; rewritten from a unix-epoch field).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "pb": {
+          "description": "Price-to-book at this date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "pe": {
+          "description": "Price-to-earnings at this date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "IndustryValuationItem": {
+      "description": "One peer in `industry_valuation`'s `list`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "dividend_yield": {
+          "description": "Dividend yield.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "history": {
+          "description": "Per-date history of PE/PB.",
+          "items": {
+            "$ref": "#/$defs/IndustryValuationHistoryPoint"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Display name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "pb": {
+          "description": "Price-to-book.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "pe": {
+          "description": "Price-to-earnings.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "ps": {
+          "description": "Price-to-sales.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol": {
+          "description": "Security symbol (transformed from `counter_id`).",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `industry_valuation`. Wraps a `list` of industry peers.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "list": {
+      "description": "Peers in the same industry.",
+      "items": {
+        "$ref": "#/$defs/IndustryValuationItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "IndustryValuationResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond the annotations—no mention of output shape, data scope, or edge cases. It does not contradict the annotations, but it also does not add meaningful behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no wasted words. It is front-loaded with the verb and resource. However, it is so terse that it sacrifices useful detail, which keeps it from a 5.

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?

Given the large number of closely related sibling tools and no output schema, the description is too thin. An agent cannot tell what 'industry valuation comparison' returns, how it differs from industry_valuation_dist or valuation_comparison, or what the output looks like. The annotations cover safety but not selection or output expectations.

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%, so the schema already documents both parameters. The description adds no parameter-level meaning beyond what the schema provides. Baseline 3 is appropriate because the schema carries the full burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get industry valuation comparison for peers' states a clear verb and resource, but it is vague about what exactly is compared (valuation metrics? multiples?) and how it differs from closely related siblings like industry_peers, industry_rank, industry_valuation_dist, valuation_comparison, and valuation_rank. It names the general purpose but does not distinguish it from these alternatives.

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?

No guidance is given on when to use this tool versus the many sibling tools with overlapping names (industry_peers, industry_rank, industry_valuation_dist, valuation_comparison, valuation_rank). The description does not state any exclusions, prerequisites, or context for selection.

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