longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Investor Relations

invest_relation

Read-onlyIdempotent

Fetch investor relations events and announcements for any stock symbol to track earnings calls, shareholder meetings, and disclosures.

Instructions

Get investor relations events and announcements.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`_jq`	No	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.
`symbol`	Yes	Security 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.

Changed2 schema fields changedv0.12.0Sep 23, 2026

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."

Changed2 schema fields changedv0.10.6Sep 10, 2026

addedInput schema / properties / _jq
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "InvestRelationItem": {
-      "properties": {
-        "description": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "event_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "event_type": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "title": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "url": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "items": {
-      "items": {
-        "$ref": "#/$defs/InvestRelationItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed2 schema fields changedv0.8.7Aug 19, 2026
- addedOutput schema / $defs / InvestRelationItem / properties / description
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / $defs / InvestRelationItem / properties / title
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"SymbolParam"
```

Changed10 schema fields changedv0.6.0Jun 26, 2026

removedOutput schema / $defs / InvestRelationItem / description

Removed value: -"One event in `invest_relation`'s `items`.\n\nSubset of documented fields; upstream may return more."

removedOutput schema / $defs / InvestRelationItem / properties / description

Removed value: -{
-  "description": "Free-text description.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / $defs / InvestRelationItem / properties / event_date / description
```
Removed value: -"Event date."
```
removedOutput schema / $defs / InvestRelationItem / properties / event_type / description
```
Removed value: -"Event type."
```

removedOutput schema / $defs / InvestRelationItem / properties / title

Removed value: -{
-  "description": "Event title.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / $defs / InvestRelationItem / properties / url / description
```
Removed value: -"Related URL."
```

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / description

Removed value: -"Returned by `invest_relation`. Wraps an `items` array of IR events.\n\nSubset of documented fields; upstream may return more."

removedOutput schema / properties / items / description

Removed value: -"Investor-relations events and announcements."

removedOutput schema / title

Removed value: -"InvestRelationResponse"

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "InvestRelationItem": {
+      "description": "One event in `invest_relation`'s `items`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "description": {
+          "description": "Free-text description.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "event_date": {
+          "description": "Event date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "event_type": {
+          "description": "Event type.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "title": {
+          "description": "Event title.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "url": {
+          "description": "Related URL.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `invest_relation`. Wraps an `items` array of IR events.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "items": {
+      "description": "Investor-relations events and announcements.",
+      "items": {
+        "$ref": "#/$defs/InvestRelationItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "InvestRelationResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
First observedv0.1.12May 8, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data and the description is consistent with it. However, the description adds no behavioral context beyond the annotations — it doesn't mention return shape, pagination, or whether this reflects historical vs. upcoming events, so credit is limited to consistency.

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 zero wasted words. It states the verb and the resource immediately and contains no filler or redundant elaboration.

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?

For a simple read-only tool with one required parameter and full schema coverage, the description is minimally adequate. Yet it never specifies the nature of the events/announcements, the time window covered, or the output shape (no output schema exists to compensate), and it doesn't help disambiguate against similar siblings, so completeness is only average.

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% (both symbol and _jq are documented in the schema), so per rubric the baseline is 3 even though the description adds no parameter detail. The description doesn't clarify what event types or announcement kinds are returned for a given symbol, but the schema already carries the parameter documentation burden.

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') with a resource ('investor relations events and announcements'), which is clear at a basic level. However, with 100+ siblings including news, filings, corp_action, and news_search, it doesn't distinguish itself — 'announcements' could plausibly overlap with news or filings, so the tool identity is not sharply delineated.

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 given on when to prefer invest_relation over alternatives like news, news_detail, filings, or corp_action. With a sibling set this large and several tools that could return announcements or corporate events, the absence of any selection criteria forces the agent to guess based on 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

Investor Relations

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools