Skip to main content
Glama
longbridge

longbridge

Official

Valuation History

valuation_history
Read-onlyIdempotent

Retrieve detailed valuation history time series for any security symbol to analyze past valuation trends and inform investment decisions.

Instructions

Get detailed valuation history time series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesSecurity symbol, e.g. "700.HK"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
historyNo

Schema Changelog

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

  1. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  2. Changed14 schema fields changedv0.6.0
    • removedOutput schema / $defs / ValuationHistoryBlock / description
      Removed value: -"`history` block of `valuation_history`."
    • removedOutput schema / $defs / ValuationHistoryBlock / properties / metrics / description
      Removed value: -"Per-indicator time series."
    • removedOutput schema / $defs / ValuationHistoryMetrics / description
      Removed value: -"`history.metrics` block of `valuation_history`. Each indicator is an array\nof time-series samples.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / ValuationHistoryMetrics / properties / dividend_yield / description
      Removed value: -"Dividend-yield series."
    • removedOutput schema / $defs / ValuationHistoryMetrics / properties / pb / description
      Removed value: -"Price-to-book series."
    • removedOutput schema / $defs / ValuationHistoryMetrics / properties / pe / description
      Removed value: -"Price-to-earnings series."
    • removedOutput schema / $defs / ValuationHistoryMetrics / properties / ps / description
      Removed value: -"Price-to-sales series."
    • removedOutput schema / $defs / ValuationHistoryPoint / description
      Removed value: -"One sample in a `valuation_history` metric time series.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / ValuationHistoryPoint / properties / timestamp / description
      Removed value: -"Sample timestamp (RFC3339; rewritten from a unix-epoch field)."
    • removedOutput schema / $defs / ValuationHistoryPoint / properties / value / description
      Removed value: -"Metric value at this timestamp."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `valuation_history`. Time-series valuation metrics grouped\nunder `history.metrics`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / history / description
      Removed value: -"History container."
    • removedOutput schema / title
      Removed value: -"ValuationHistoryResponse"
  3. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "ValuationHistoryBlock": {
      +      "description": "`history` block of `valuation_history`.",
      +      "properties": {
      +        "metrics": {
      +          "anyOf": [
      +            {
      +              "$ref": "#/$defs/ValuationHistoryMetrics"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "Per-indicator time series."
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "ValuationHistoryMetrics": {
      +      "description": "`history.metrics` block of `valuation_history`. Each indicator is an array\nof time-series samples.\n\nSubset of documented fields; upstream may return more.",
      +      "properties": {
      +        "dividend_yield": {
      +          "description": "Dividend-yield series.",
      +          "items": {
      +            "$ref": "#/$defs/ValuationHistoryPoint"
      +          },
      +          "type": [
      +            "array",
      +            "null"
      +          ]
      +        },
      +        "pb": {
      +          "description": "Price-to-book series.",
      +          "items": {
      +            "$ref": "#/$defs/ValuationHistoryPoint"
      +          },
      +          "type": [
      +            "array",
      +            "null"
      +          ]
      +        },
      +        "pe": {
      +          "description": "Price-to-earnings series.",
      +          "items": {
      +            "$ref": "#/$defs/ValuationHistoryPoint"
      +          },
      +          "type": [
      +            "array",
      +            "null"
      +          ]
      +        },
      +        "ps": {
      +          "description": "Price-to-sales series.",
      +          "items": {
      +            "$ref": "#/$defs/ValuationHistoryPoint"
      +          },
      +          "type": [
      +            "array",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "ValuationHistoryPoint": {
      +      "description": "One sample in a `valuation_history` metric time series.\n\nSubset of documented fields; upstream may return more.",
      +      "properties": {
      +        "timestamp": {
      +          "description": "Sample timestamp (RFC3339; rewritten from a unix-epoch field).",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "value": {
      +          "description": "Metric value at this timestamp.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "description": "Returned by `valuation_history`. Time-series valuation metrics grouped\nunder `history.metrics`.\n\nSubset of documented fields; upstream may return more.",
      +  "properties": {
      +    "history": {
      +      "anyOf": [
      +        {
      +          "$ref": "#/$defs/ValuationHistoryBlock"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "History container."
      +    }
      +  },
      +  "title": "ValuationHistoryResponse",
      +  "type": "object"
      +}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. First observedv0.1.12

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the description adds minimal behavioral context. It says 'detailed' but does not elaborate on data frequency, pagination, or other behavioral traits.

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 a single, front-loaded sentence with no extraneous words. Every word contributes to clarity.

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?

Despite having an output schema, the description could hint at the types of valuation metrics included. However, given the schema and annotations, it is adequately complete for selection.

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 coverage is 100%, meaning the schema fully documents the single parameter 'symbol'. The description adds no extra meaning beyond what the schema provides.

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

Purpose5/5

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

The description uses a specific verb ('Get') and resource ('valuation history time series'), clearly distinguishing it from siblings like 'valuation' (snapshot) and 'valuation_comparison' (comparison).

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 explicit guidance on when to use this tool versus alternatives like 'valuation' or 'valuation_history'. The description lacks usage context or exclusions.

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

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