industry_valuation_distGet industry valuation distribution (PE, PB, PS) for a security symbol to compare its standing against sector peers. Use this to gauge relative valuation levels.
Get industry PE/PB/PS valuation distribution.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Security symbol, e.g. "700.HK" |
| Name | Required | Description | Default |
|---|---|---|---|
| distributions | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.7.1Input schema / titleRemoved value: -"SymbolParam"v0.6.0Output schema / $defs / IndustryValuationDistribution / descriptionRemoved value: -"One indicator's distribution stats in `industry_valuation_dist`.\n\nSubset of documented fields; upstream may return more."Output schema / $defs / IndustryValuationDistribution / properties / current_percentile / descriptionRemoved value: -"Where the stock currently sits in this distribution."Output schema / $defs / IndustryValuationDistribution / properties / max / descriptionRemoved value: -"Maximum value."Output schema / $defs / IndustryValuationDistribution / properties / median / descriptionRemoved value: -"Median."Output schema / $defs / IndustryValuationDistribution / properties / min / descriptionRemoved value: -"Minimum value."Output schema / $defs / IndustryValuationDistribution / properties / p25 / descriptionRemoved value: -"25th percentile."Output schema / $defs / IndustryValuationDistribution / properties / p75 / descriptionRemoved value: -"75th percentile."Output schema / $defs / IndustryValuationDistributions / descriptionRemoved value: -"`distributions` block of `industry_valuation_dist`.\n\nSubset of documented fields; upstream may return more."Output schema / $defs / IndustryValuationDistributions / properties / pb / descriptionRemoved value: -"Price-to-book distribution."Output schema / $defs / IndustryValuationDistributions / properties / pe / descriptionRemoved value: -"Price-to-earnings distribution."Output schema / $defs / IndustryValuationDistributions / properties / ps / descriptionRemoved value: -"Price-to-sales distribution."Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Output schema / descriptionRemoved value: -"Returned by `industry_valuation_dist`. Per-indicator distribution stats\ngrouped under `distributions`.\n\nSubset of documented fields; upstream may return more."Output schema / properties / distributions / descriptionRemoved value: -"Per-indicator distribution blocks."Output schema / titleRemoved value: -"IndustryValuationDistResponse"v0.5.6Output 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"
+}v0.4.5v0.4.0v0.3.2v0.3.1v0.1.12Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool as readOnly, idempotent, and non-destructive. The description adds that it returns a 'distribution' of PE/PB/PS values, which is behavioral context beyond annotations, but does not disclose the format (e.g., histogram, percentiles) or any time scope.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, which is concise but may be overly terse. It states the core purpose without elaboration, which is acceptable but leaves room for ambiguity about the nature of the 'distribution'.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so the description does not need to detail return values. However, the tool deals with valuation distributions and could benefit from additional context (e.g., whether it returns historical or current data, or how industries are defined). Given moderate complexity and good schema coverage, it is minimally adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'symbol' is fully described in the schema (100% coverage) with an example. The description adds no additional semantic meaning, so a baseline 3 is appropriate given the schema already handles it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves 'industry PE/PB/PS valuation distribution', specifying the exact valuation metrics. However, it does not differentiate from siblings like 'industry_valuation' (likely summary stats) or 'industry_rank', leaving the agent to infer the distinction from the term 'distribution'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as 'industry_valuation' or 'industry_peers'. There is no mention of prerequisites, limitations, or context-specific scenarios, leaving the agent without decision support.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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