Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Corporate Actions

corp_action
Read-onlyIdempotent

Fetch corporate actions like splits, buybacks, and name changes by security symbol. Input a canonical symbol to retrieve actionable data for analysis.

Instructions

Get corporate actions (splits, buybacks, name changes).

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": {
-    "CorpActionItem": {
-      "properties": {
-        "action_type": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "description": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "effective_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "ratio": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "items": {
-      "items": {
-        "$ref": "#/$defs/CorpActionItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.8.7
    • addedOutput schema / $defs / CorpActionItem / properties / description
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  4. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  5. Changed9 schema fields changedv0.6.0
    • removedOutput schema / $defs / CorpActionItem / description
      Removed value: -"One event in `corp_action`'s `items`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / CorpActionItem / properties / action_type / description
      Removed value: -"Action type (split, buyback, name change, ...)."
    • removedOutput schema / $defs / CorpActionItem / properties / description
      Removed value: -{
-  "description": "Free-text description.",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • removedOutput schema / $defs / CorpActionItem / properties / effective_date / description
      Removed value: -"Effective date."
    • removedOutput schema / $defs / CorpActionItem / properties / ratio / description
      Removed value: -"Ratio (e.g. for splits)."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `corp_action`. Wraps an `items` array of corporate actions.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / items / description
      Removed value: -"Corporate action events."
    • removedOutput schema / title
      Removed value: -"CorpActionResponse"
  6. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "CorpActionItem": {
+      "description": "One event in `corp_action`'s `items`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "action_type": {
+          "description": "Action type (split, buyback, name change, ...).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "description": {
+          "description": "Free-text description.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "effective_date": {
+          "description": "Effective date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "ratio": {
+          "description": "Ratio (e.g. for splits).",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `corp_action`. Wraps an `items` array of corporate actions.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "items": {
+      "description": "Corporate action events.",
+      "items": {
+        "$ref": "#/$defs/CorpActionItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "CorpActionResponse",
+  "type": "object"
+}
  7. Addedv0.4.5
  8. Removedv0.4.0
  9. Addedv0.3.2
  10. Removedv0.3.1
  11. First observedv0.1.12

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already convey readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds the examples of corporate action types, which is mild context beyond the annotations, but it does not disclose additional behaviors like pagination, filtering, or output shape. It adds some value but not substantial.

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 focused sentence with no filler. It front-loads the action ('Get') and immediately clarifies scope with examples. Every word earns its place.

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

Completeness3/5

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

The tool is simple and read-only with rich annotations, but there is no output schema and the description does not hint at the return format or any usage nuances. Given the simplicity, it is mostly adequate, but it misses a note about what the response structure looks like, leaving the agent to guess.

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%, so the schema already documents both symbol and _jq parameters thoroughly. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 applies.

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 states a clear verb ('Get') and resource ('corporate actions'), and lists specific examples (splits, buybacks, name changes) that clarify scope. However, it does not explicitly differentiate from sibling tools like dividend or capital_distribution, which cover overlapping events.

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 alternatives. The description is terse and gives no context about selection criteria, such as 'use this for all corporate actions, dividend for dividend-specific data'.

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