longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Institution Rating Detail

institution_rating_detail

Read-onlyIdempotent

Retrieve historical institution ratings and target price history for a given security symbol. Use this tool to analyze analyst sentiment and price target trends.

Instructions

Get detailed historical institution ratings and target price 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_detail"
  }
}

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": {
-    "InstitutionRatingDetailItem": {
-      "properties": {
-        "analyst": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "firm": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "rating": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "target_price": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "timestamp": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "InstitutionRatingDetailTarget": {
-      "properties": {
-        "list": {
-          "items": {
-            "$ref": "#/$defs/InstitutionRatingDetailItem"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "target": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/InstitutionRatingDetailTarget"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"SymbolParam"
```
Changed12 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / InstitutionRatingDetailItem / description
```
Removed value: -"One per-institution record in `institution_rating_detail`'s `target.list`.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / $defs / InstitutionRatingDetailItem / properties / analyst / description
```
Removed value: -"Analyst name."
```
- removedOutput schema / $defs / InstitutionRatingDetailItem / properties / firm / description
```
Removed value: -"Issuing firm / institution name."
```
- removedOutput schema / $defs / InstitutionRatingDetailItem / properties / rating / description
```
Removed value: -"Rating label."
```
- removedOutput schema / $defs / InstitutionRatingDetailItem / properties / target_price / description
```
Removed value: -"Target price."
```
- removedOutput schema / $defs / InstitutionRatingDetailItem / properties / timestamp / description
```
Removed value: -"Rating timestamp (RFC3339; rewritten from a unix-epoch field)."
```
- removedOutput schema / $defs / InstitutionRatingDetailTarget / description
```
Removed value: -"`target` block of `institution_rating_detail`."
```
- removedOutput schema / $defs / InstitutionRatingDetailTarget / properties / list / description
```
Removed value: -"Per-institution rating records."
```
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / description
```
Removed value: -"Returned by `institution_rating_detail`.\n\nDetailed historical institution ratings and target price history, grouped\nunder `target.list[]`. Subset of documented fields; upstream may return\nmore."
```
- removedOutput schema / properties / target / description
```
Removed value: -"Target-price / rating history container."
```
- removedOutput schema / title
```
Removed value: -"InstitutionRatingDetailResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "InstitutionRatingDetailItem": {
+      "description": "One per-institution record in `institution_rating_detail`'s `target.list`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "analyst": {
+          "description": "Analyst name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "firm": {
+          "description": "Issuing firm / institution name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "rating": {
+          "description": "Rating label.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "target_price": {
+          "description": "Target price.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "timestamp": {
+          "description": "Rating timestamp (RFC3339; rewritten from a unix-epoch field).",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "InstitutionRatingDetailTarget": {
+      "description": "`target` block of `institution_rating_detail`.",
+      "properties": {
+        "list": {
+          "description": "Per-institution rating records.",
+          "items": {
+            "$ref": "#/$defs/InstitutionRatingDetailItem"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `institution_rating_detail`.\n\nDetailed historical institution ratings and target price history, grouped\nunder `target.list[]`. Subset of documented fields; upstream may return\nmore.",
+  "properties": {
+    "target": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/InstitutionRatingDetailTarget"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Target-price / rating history container."
+    }
+  },
+  "title": "InstitutionRatingDetailResponse",
+  "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

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no additional behavioral disclosure such as rate limits, pagination, error behavior, or the canonical symbol requirement, which is only in the parameter description.

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

Conciseness4/5

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

The description is a single concise sentence with no superfluous words. It front-loads the action and resource effectively. It could be slightly more informative about the 'detail' aspect, but it remains appropriately sized.

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 description is adequate for a simple read-only tool with one required parameter and no output schema. However, it does not differentiate from closely named siblings like institution_rating_history, leaving ambiguity about when to choose this tool. The canonical symbol caveat is covered in the schema, so it does not need to be in the description.

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% for both parameters (symbol and _jq), so the schema already provides complete parameter documentation. The tool description adds no extra meaning beyond what is in the schema, so baseline 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 clearly states a specific action and resource: 'Get detailed historical institution ratings and target price history.' It is clear but does not explicitly distinguish itself from sibling tools like institution_rating_history or institution_rating, relying on the 'detail' in the name for differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention conditions, prerequisites, or exclusions. It is purely a purpose statement without any usage context.

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

Deploy Server