longbridge

Official

by longbridge

Overview Schema Source Related Servers Score Discussions(1)Admin

Rust

Hybrid

Valuation

valuation

Read-onlyIdempotent

Compare a company's market worth with peer stocks for a given security symbol.

Instructions

Get valuation overview with peer comparison. US accounts querying a .US symbol get a differently-shaped response not matching output_schema (ai_summary plus a metrics.pe object with different sub-fields); other combos match output_schema.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	Yes	Security symbol, e.g. "700.HK"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No
`range`	No
`metrics`	No
`indicator`	No
`ai_summary`	No
`ccy_symbol`	No

Schema Changelog

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

Changed8 schema fields changedv0.8.4Jul 25, 2026

addedOutput schema / $defs / ValuationMetric / properties / desc

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / $defs / ValuationMetric / properties / industry_median

Added value: +{
+  "format": "double",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / $defs / ValuationMetric / properties / metric

Added value: +{
+  "format": "double",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / ai_summary

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / ccy_symbol

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / date

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / indicator

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / range

Added value: +{
+  "format": "int32",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"SymbolParam"
```
Changed14 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / ValuationMetric / description
```
Removed value: -"A single valuation indicator block in `valuation`.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / $defs / ValuationMetric / properties / 5yr_avg / description
```
Removed value: -"5-year average. (camelCase `5yr_avg` per description.)"
```
- removedOutput schema / $defs / ValuationMetric / properties / current / description
```
Removed value: -"Current value."
```
- removedOutput schema / $defs / ValuationMetric / properties / industry_avg / description
```
Removed value: -"Industry average."
```
- removedOutput schema / $defs / ValuationMetric / properties / percentile / description
```
Removed value: -"Historical percentile."
```
- removedOutput schema / $defs / ValuationMetrics / description
```
Removed value: -"`metrics` block of `valuation`. Each indicator carries the same shape.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / $defs / ValuationMetrics / properties / dividend_yield / description
```
Removed value: -"Dividend-yield block."
```
- removedOutput schema / $defs / ValuationMetrics / properties / pb / description
```
Removed value: -"Price-to-book block."
```
- removedOutput schema / $defs / ValuationMetrics / properties / pe / description
```
Removed value: -"Price-to-earnings block."
```
- removedOutput schema / $defs / ValuationMetrics / properties / ps / description
```
Removed value: -"Price-to-sales block."
```
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / description
```
Removed value: -"Returned by `valuation`. The valuation overview groups per-metric blocks\nunder `metrics`.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / properties / metrics / description
```
Removed value: -"Valuation metric blocks keyed by indicator."
```
- removedOutput schema / title
```
Removed value: -"ValuationResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ValuationMetric": {
+      "description": "A single valuation indicator block in `valuation`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "5yr_avg": {
+          "description": "5-year average. (camelCase `5yr_avg` per description.)",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "current": {
+          "description": "Current value.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "industry_avg": {
+          "description": "Industry average.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "percentile": {
+          "description": "Historical percentile.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "ValuationMetrics": {
+      "description": "`metrics` block of `valuation`. Each indicator carries the same shape.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "dividend_yield": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/ValuationMetric"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Dividend-yield block."
+        },
+        "pb": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/ValuationMetric"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Price-to-book block."
+        },
+        "pe": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/ValuationMetric"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Price-to-earnings block."
+        },
+        "ps": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/ValuationMetric"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Price-to-sales block."
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `valuation`. The valuation overview groups per-metric blocks\nunder `metrics`.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "metrics": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/ValuationMetrics"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Valuation metric blocks keyed by indicator."
+    }
+  },
+  "title": "ValuationResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
First observedv0.1.12May 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds critical transparency: for US accounts querying a .US symbol, the response shape differs from the output schema. This detail about output variability goes beyond what annotations provide, aiding correct interpretation.

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 extremely concise, consisting of two sentences. The first sentence states the core purpose, and the second provides a crucial behavioral caveat. No superfluous words; information is front-loaded and efficient.

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

Completeness4/5

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

Given the simple parameter set and the presence of an output schema, the description adequately covers the special output shape discrepancy. It does not need to explain standard return values. The mention of peer comparison adds context. Completeness is high for a tool of this complexity.

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?

Schema coverage is 100% with a clear description for the 'symbol' parameter. The description adds semantic value by linking the parameter value to a behavioral change: different response shapes for .US symbols. This informs the agent about a conditional effect of the parameter.

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 clearly states the tool retrieves a 'valuation overview with peer comparison', providing a specific verb and resource. It differentiates from siblings like 'valuation_comparison' by noting an output shape quirk for US .US symbols, but does not explicitly contrast with all sister tools.

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?

The description implies usage for obtaining valuation with peer comparison and warns about a special case for US accounts with .US symbols. However, it does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among the many sibling tools.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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