Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

Dividend

dividend
Read-onlyIdempotent

Retrieve dividend history for a security symbol to analyze past payouts and yields. Supports US and HK markets with symbol-specific response formats.

Instructions

Get dividend history for the symbol. US accounts querying a .US symbol get a differently-shaped response not matching output_schema (dividend_yield_ttm etc. are percent values, e.g. 0.34 means 0.34%); other combinations match output_schema.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNo
payout_ratiosNo
dividend_historyNo
recent_dividendsNo
dividend_payout_historyNo

Schema Changelog

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

  1. Changed7 schema fields changedv0.8.4
    • addedOutput schema / $defs / UsDividendHistoryYear
      Added value: +{
+  "properties": {
+    "currency": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dividend": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dividend_growth_rate": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dividend_payout_ratio": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dividend_to_cashflow_ratio": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dividend_yield": {
+      "format": "double",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "fiscal_year": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "fiscal_year_range": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / $defs / UsDividendPayout
      Added value: +{
+  "properties": {
+    "currency": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dividend": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dividend_type": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ex_date": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "payment_date": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "record_date": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / $defs / UsRecentDividends
      Added value: +{
+  "properties": {
+    "currency": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dividend_ttm": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dividend_yield_ttm": {
+      "format": "double",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "payouts": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / dividend_history
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/UsDividendHistoryYear"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}
    • addedOutput schema / properties / dividend_payout_history
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/UsDividendPayout"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}
    • addedOutput schema / properties / payout_ratios
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/UsDividendHistoryYear"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}
    • addedOutput schema / properties / recent_dividends
      Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/UsRecentDividends"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
  2. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  3. Changed12 schema fields changedv0.6.0
    • removedOutput schema / $defs / DividendItem / description
      Removed value: -"One dividend event in `dividend`'s `items`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / DividendItem / properties / amount / description
      Removed value: -"Dividend amount."
    • removedOutput schema / $defs / DividendItem / properties / currency / description
      Removed value: -"Settlement currency."
    • removedOutput schema / $defs / DividendItem / properties / dividend_type / description
      Removed value: -"Dividend type."
    • removedOutput schema / $defs / DividendItem / properties / ex_date / description
      Removed value: -"Ex-dividend date."
    • removedOutput schema / $defs / DividendItem / properties / pay_date / description
      Removed value: -"Payment date."
    • removedOutput schema / $defs / DividendItem / properties / record_date / description
      Removed value: -"Record date."
    • removedOutput schema / $defs / DividendItem / properties / status / description
      Removed value: -"Dividend status."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `dividend`. Wraps an `items` array of dividend events.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / items / description
      Removed value: -"Dividend events for the symbol."
    • removedOutput schema / title
      Removed value: -"DividendResponse"
  4. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "DividendItem": {
+      "description": "One dividend event in `dividend`'s `items`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "amount": {
+          "description": "Dividend amount.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "currency": {
+          "description": "Settlement currency.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "dividend_type": {
+          "description": "Dividend type.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "ex_date": {
+          "description": "Ex-dividend date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "pay_date": {
+          "description": "Payment date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "record_date": {
+          "description": "Record date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "description": "Dividend status.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `dividend`. Wraps an `items` array of dividend events.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "items": {
+      "description": "Dividend events for the symbol.",
+      "items": {
+        "$ref": "#/$defs/DividendItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "DividendResponse",
+  "type": "object"
+}
  5. Addedv0.4.5
  6. Removedv0.4.0
  7. Addedv0.3.2
  8. Removedv0.3.1
  9. First observedv0.1.12

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds behavioral context about response shape variation for US accounts and percent value interpretation, which is not covered by 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 sentences with zero waste. First sentence states core purpose, second adds critical caveat. No redundant information.

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

Completeness5/5

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

Tool has one parameter, good annotations, and an output schema exists (noted in description). The description covers the main behavior and a key exception, sufficient for a simple query tool.

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?

Input schema has 100% coverage with a single symbol parameter. Description adds semantic nuance by explaining that the response shape depends on the symbol and account type, going beyond the schema's definition.

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?

Description states 'Get dividend history for the symbol' with a specific verb and resource. It distinguishes from siblings by noting a special response case for US accounts querying .US symbols.

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?

No explicit when-to-use or alternative tools mentioned. The description implies caution for US accounts with .US symbols but does not compare to sibling tools like dividend_detail.

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