industry_valuationCompare a security's valuation against its industry peers by submitting its symbol, revealing relative value and sector positioning.
Get industry valuation comparison for peers.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Security symbol, e.g. "700.HK" |
| Name | Required | Description | Default |
|---|---|---|---|
| list | 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 / IndustryValuationHistoryPoint / descriptionRemoved value: -"One history point in `industry_valuation`'s nested `history`.\n\nSubset of documented fields; upstream may return more."Output schema / $defs / IndustryValuationHistoryPoint / properties / date / descriptionRemoved value: -"Sample date (RFC3339; rewritten from a unix-epoch field)."Output schema / $defs / IndustryValuationHistoryPoint / properties / pb / descriptionRemoved value: -"Price-to-book at this date."Output schema / $defs / IndustryValuationHistoryPoint / properties / pe / descriptionRemoved value: -"Price-to-earnings at this date."Output schema / $defs / IndustryValuationItem / descriptionRemoved value: -"One peer in `industry_valuation`'s `list`.\n\nSubset of documented fields; upstream may return more."Output schema / $defs / IndustryValuationItem / properties / dividend_yield / descriptionRemoved value: -"Dividend yield."Output schema / $defs / IndustryValuationItem / properties / history / descriptionRemoved value: -"Per-date history of PE/PB."Output schema / $defs / IndustryValuationItem / properties / name / descriptionRemoved value: -"Display name."Output schema / $defs / IndustryValuationItem / properties / pb / descriptionRemoved value: -"Price-to-book."Output schema / $defs / IndustryValuationItem / properties / pe / descriptionRemoved value: -"Price-to-earnings."Output schema / $defs / IndustryValuationItem / properties / ps / descriptionRemoved value: -"Price-to-sales."Output schema / $defs / IndustryValuationItem / properties / symbol / descriptionRemoved value: -"Security symbol (transformed from `counter_id`)."Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Output schema / descriptionRemoved value: -"Returned by `industry_valuation`. Wraps a `list` of industry peers.\n\nSubset of documented fields; upstream may return more."Output schema / properties / list / descriptionRemoved value: -"Peers in the same industry."Output schema / titleRemoved value: -"IndustryValuationResponse"v0.5.6Output 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"
+}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 read-only, idempotent, and non-destructive. The description adds no further behavioral context, but the bar is lower due to annotation coverage.
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, concise sentence that front-loads the key action and object, with no unnecessary words.
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?
While the output schema likely details the return values, the description does not explain what 'valuation comparison' entails (e.g., metrics like P/E, P/B). It is adequate but could be more informative.
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?
Schema coverage is 100% with a clear parameter description. The description does not add any additional meaning beyond the schema, so baseline score of 3 is appropriate.
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 uses a specific verb 'Get' and identifies the resource 'industry valuation comparison for peers', clearly distinguishing it from sibling tools like 'valuation' or 'industry_rank'.
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 'valuation_comparison' or 'industry_valuation_dist', leaving the agent to infer the appropriate context.
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