Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Dividend Detail

dividend_detail
Read-onlyIdempotent

Need dividend details? Provide a security symbol to retrieve its complete distribution scheme, including payout dates and amounts for informed investment decisions.

Instructions

Get detailed dividend distribution scheme.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response.
symbolYesSecurity symbol, e.g. "700.HK". Use the canonical form — a padded code like "00700.HK" returns an empty record, not an error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.0
    • addedInput schema / properties / _jq / description
      Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."
    • changedInput schema / properties / symbol / description
      Previous value: -"Security symbol, e.g. \"700.HK\""New value: +"Security symbol, e.g. \"700.HK\". Use the canonical form — a padded code like \"00700.HK\" returns an empty record, not an error."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "DividendDetailItem": {
-      "properties": {
-        "cash_dividend": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "currency": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "ex_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "pay_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "period": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "record_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "stock_dividend": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "details": {
-      "items": {
-        "$ref": "#/$defs/DividendDetailItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  4. Changed12 schema fields changedv0.6.0
    • removedOutput schema / $defs / DividendDetailItem / description
      Removed value: -"One distribution scheme in `dividend_detail`'s `details`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / DividendDetailItem / properties / cash_dividend / description
      Removed value: -"Cash dividend per share."
    • removedOutput schema / $defs / DividendDetailItem / properties / currency / description
      Removed value: -"Settlement currency."
    • removedOutput schema / $defs / DividendDetailItem / properties / ex_date / description
      Removed value: -"Ex-dividend date."
    • removedOutput schema / $defs / DividendDetailItem / properties / pay_date / description
      Removed value: -"Payment date."
    • removedOutput schema / $defs / DividendDetailItem / properties / period / description
      Removed value: -"Reporting period."
    • removedOutput schema / $defs / DividendDetailItem / properties / record_date / description
      Removed value: -"Record date."
    • removedOutput schema / $defs / DividendDetailItem / properties / stock_dividend / description
      Removed value: -"Stock dividend ratio / amount."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `dividend_detail`. Wraps a `details` array of distribution\nschemes.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / details / description
      Removed value: -"Per-period distribution schemes."
    • removedOutput schema / title
      Removed value: -"DividendDetailResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "DividendDetailItem": {
+      "description": "One distribution scheme in `dividend_detail`'s `details`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "cash_dividend": {
+          "description": "Cash dividend per share.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "currency": {
+          "description": "Settlement currency.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "ex_date": {
+          "description": "Ex-dividend date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "pay_date": {
+          "description": "Payment date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "period": {
+          "description": "Reporting period.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "record_date": {
+          "description": "Record date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "stock_dividend": {
+          "description": "Stock dividend ratio / amount.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `dividend_detail`. Wraps a `details` array of distribution\nschemes.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "details": {
+      "description": "Per-period distribution schemes.",
+      "items": {
+        "$ref": "#/$defs/DividendDetailItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "DividendDetailResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds no behavioral traits beyond 'detailed', but it also does not contradict the annotations, so the safety profile is adequately covered.

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?

A single, front-loaded sentence with no filler. It communicates the core action efficiently and is appropriately sized for a simple read-only getter.

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?

With no output schema, the description should clarify what the response contains or how this tool differs from simpler dividend tools. Saying 'detailed dividend distribution scheme' is too vague to guide the agent on expected return data, and no usage context or alternatives are given.

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 description coverage is 100%, and both parameters are thoroughly documented in the schema, including the canonical symbol format and the _jq filter semantics. The description adds no additional parameter meaning beyond what the schema already provides.

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 uses a specific verb ('Get') and a specific resource ('detailed dividend distribution scheme'). The word 'detailed' helps distinguish it from the sibling tool 'dividend', though the exact meaning of 'distribution scheme' remains somewhat vague.

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 guidance is provided on when to use this tool versus related siblings like 'dividend' or 'capital_distribution'. It does not state any conditions, exclusions, or alternatives, leaving the agent to infer usage from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools