longbridge

Official

by longbridge

Overview Schema Source Related Servers Score Discussions(1)Admin

Rust

Hybrid

Stock Comparison

valuation_comparison

Read-onlyIdempotent

Compare a stock's valuation against industry peers by providing a symbol and currency. Returns the stock with automatically selected peer comparisons for quick valuation context.

Instructions

Stock valuation comparison. Mode A (single): pass only symbol — server returns stock + auto-selected industry peers.

Input Schema

TableJSON Schema

Name	Required	Description
`symbol`	Yes	Security symbol to compare, e.g. "AAPL.US"
`currency`	Yes	Currency: "USD" \| "HKD" \| "CNY"
`comparison_symbols`	No	Comparison symbols, comma-separated, max 4, e.g. "MSFT.US,GOOGL.US". Note: pending backend support — currently server auto-selects industry peers.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`list`	No

Schema Changelog

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

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"ValuationComparisonParam"
```
Changed18 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / ValuationComparisonHistoryPoint / description
```
Removed value: -"One history point in `valuation_comparison`'s nested `history`.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / $defs / ValuationComparisonHistoryPoint / properties / date / description
```
Removed value: -"Sample date (RFC3339; rewritten from a unix-epoch field)."
```
- removedOutput schema / $defs / ValuationComparisonHistoryPoint / properties / pb / description
```
Removed value: -"Price-to-book at this date."
```
- removedOutput schema / $defs / ValuationComparisonHistoryPoint / properties / pe / description
```
Removed value: -"Price-to-earnings at this date."
```
- removedOutput schema / $defs / ValuationComparisonHistoryPoint / properties / ps / description
```
Removed value: -"Price-to-sales at this date."
```
- removedOutput schema / $defs / ValuationComparisonItem / description
```
Removed value: -"One stock in `valuation_comparison`'s `list`.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / $defs / ValuationComparisonItem / properties / history / description
```
Removed value: -"Per-date valuation history."
```
- removedOutput schema / $defs / ValuationComparisonItem / properties / market_value / description
```
Removed value: -"Market value."
```
- removedOutput schema / $defs / ValuationComparisonItem / properties / name / description
```
Removed value: -"Display name."
```
- removedOutput schema / $defs / ValuationComparisonItem / properties / pb / description
```
Removed value: -"Price-to-book."
```
- removedOutput schema / $defs / ValuationComparisonItem / properties / pe / description
```
Removed value: -"Price-to-earnings."
```
- removedOutput schema / $defs / ValuationComparisonItem / properties / price_close / description
```
Removed value: -"Latest close price."
```
- removedOutput schema / $defs / ValuationComparisonItem / properties / ps / description
```
Removed value: -"Price-to-sales."
```
- removedOutput schema / $defs / ValuationComparisonItem / 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 `valuation_comparison`. Wraps a `list` of compared stocks.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / properties / list / description
```
Removed value: -"Compared stocks (primary + peers)."
```
- removedOutput schema / title
```
Removed value: -"ValuationComparisonResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ValuationComparisonHistoryPoint": {
+      "description": "One history point in `valuation_comparison`'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"
+          ]
+        },
+        "ps": {
+          "description": "Price-to-sales at this date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "ValuationComparisonItem": {
+      "description": "One stock in `valuation_comparison`'s `list`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "history": {
+          "description": "Per-date valuation history.",
+          "items": {
+            "$ref": "#/$defs/ValuationComparisonHistoryPoint"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "market_value": {
+          "description": "Market value.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Display name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "pb": {
+          "description": "Price-to-book.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "pe": {
+          "description": "Price-to-earnings.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "price_close": {
+          "description": "Latest close price.",
+          "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 `valuation_comparison`. Wraps a `list` of compared stocks.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "list": {
+      "description": "Compared stocks (primary + peers).",
+      "items": {
+        "$ref": "#/$defs/ValuationComparisonItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "ValuationComparisonResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly and idempotent. The description adds that the server auto-selects industry peers and that comparison_symbols is pending backend support. This provides useful behavioral context beyond 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?

Two short, front-loaded sentences with no wasted words. Efficiently communicates the core idea.

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?

The description is incomplete: it only describes Mode A, ignoring Mode B with comparison_symbols. Given the tool has a pending parameter and two modes, the description should cover both for completeness.

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%, providing baseline 3. The description adds meaning by explaining that passing only symbol triggers auto-selection of peers, and notes pending support for comparison_symbols. This clarifies parameter behavior beyond schema.

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 'Stock valuation comparison' and specifies Mode A behavior (single symbol returns stock + peers). However, it omits Mode B involving comparison_symbols, which reduces clarity about full functionality.

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 gives minimal guidance on when to use this tool versus siblings like valuation or industry_valuation. It hints at two modes but doesn't explicitly state when to pass only symbol vs. comparison_symbols.

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