longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Institution Rating History

institution_rating_history

Read-onlyIdempotent

Retrieve historical institution ratings for a security by symbol. Input a canonical symbol like 700.HK to get the full rating history.

Instructions

Get institution rating history.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "institution_rating_history"
  }
}

Input 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": {
-    "EvaluateHistoryItem": {
-      "properties": {
-        "date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "firm": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "new_rating": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "old_rating": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "TargetHistoryItem": {
-      "properties": {
-        "analyst": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "firm": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "new_target": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "old_target": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "evaluate_history": {
-      "items": {
-        "$ref": "#/$defs/EvaluateHistoryItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "target_history": {
-      "items": {
-        "$ref": "#/$defs/TargetHistoryItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"SymbolParam"
```
Changed16 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / EvaluateHistoryItem / description
```
Removed value: -"One rating-evaluation change in `institution_rating_history`.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / $defs / EvaluateHistoryItem / properties / date / description
```
Removed value: -"Change date."
```
- removedOutput schema / $defs / EvaluateHistoryItem / properties / firm / description
```
Removed value: -"Issuing firm."
```
- removedOutput schema / $defs / EvaluateHistoryItem / properties / new_rating / description
```
Removed value: -"New rating."
```
- removedOutput schema / $defs / EvaluateHistoryItem / properties / old_rating / description
```
Removed value: -"Prior rating."
```
- removedOutput schema / $defs / TargetHistoryItem / description
```
Removed value: -"One target-price revision in `institution_rating_history`.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / $defs / TargetHistoryItem / properties / analyst / description
```
Removed value: -"Analyst name."
```
- removedOutput schema / $defs / TargetHistoryItem / properties / date / description
```
Removed value: -"Revision date."
```
- removedOutput schema / $defs / TargetHistoryItem / properties / firm / description
```
Removed value: -"Issuing firm."
```
- removedOutput schema / $defs / TargetHistoryItem / properties / new_target / description
```
Removed value: -"New target price."
```
- removedOutput schema / $defs / TargetHistoryItem / properties / old_target / description
```
Removed value: -"Prior target price."
```
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / description
```
Removed value: -"Returned by `institution_rating_history`. Two history arrays: target-price\nrevisions and rating-evaluation changes.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / properties / evaluate_history / description
```
Removed value: -"Rating-evaluation changes."
```
- removedOutput schema / properties / target_history / description
```
Removed value: -"Target-price revisions."
```
- removedOutput schema / title
```
Removed value: -"InstitutionRatingHistoryResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "EvaluateHistoryItem": {
+      "description": "One rating-evaluation change in `institution_rating_history`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "date": {
+          "description": "Change date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "firm": {
+          "description": "Issuing firm.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "new_rating": {
+          "description": "New rating.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "old_rating": {
+          "description": "Prior rating.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "TargetHistoryItem": {
+      "description": "One target-price revision in `institution_rating_history`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "analyst": {
+          "description": "Analyst name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "date": {
+          "description": "Revision date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "firm": {
+          "description": "Issuing firm.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "new_target": {
+          "description": "New target price.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "old_target": {
+          "description": "Prior target price.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `institution_rating_history`. Two history arrays: target-price\nrevisions and rating-evaluation changes.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "evaluate_history": {
+      "description": "Rating-evaluation changes.",
+      "items": {
+        "$ref": "#/$defs/EvaluateHistoryItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "target_history": {
+      "description": "Target-price revisions.",
+      "items": {
+        "$ref": "#/$defs/TargetHistoryItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "InstitutionRatingHistoryResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
Addedv0.2.1May 9, 2026

TDQS

C2.8/5.0

Behavior2/5

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

The annotations already convey read-only, idempotent, and non-destructive behavior, so the description is not required to repeat that. But the description itself adds no extra behavioral context such as time range, ordering, response granularity, or record shape; 'history' merely mirrors the tool name. It does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no fluff, so it is concise in form. However, it adds little beyond the title and omits useful differentiating context; the brevity is not paired with enough substance to be genuinely effective.

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 and several closely related institution_rating sibling tools, a one-sentence description is incomplete. It does not clarify what data the history contains, what time span it covers, or how to choose this tool over institution_rating or institution_rating_detail.

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 well documented: symbol includes canonical-form guidance and an empty-record warning, and _jq explains its filtering behavior. The description adds no parameter-level insight, but the schema carries the full burden adequately.

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 specific verb ('Get') and resource ('institution rating history'), so the core purpose is clear in isolation. However, it essentially restates the tool's title and does not distinguish it from closely related siblings such as institution_rating, institution_rating_detail, or institution_rating_industry_rank.

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?

There is no guidance about when to use this tool instead of the many institution_rating-related siblings. No alternatives, exclusions, or selection criteria are mentioned, which is a significant gap given the large sibling list.

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

Deploy Server