longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Institution Rating

institution_rating

Read-onlyIdempotent

Fetch an institution rating summary for a stock symbol to view analyst recommendations and consensus.

Instructions

Get institution rating summary.

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": {
-    "InstitutionRatingAnalyst": {
-      "properties": {
-        "buy": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "consensus_rating": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "hold": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "outperform": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "sell": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "target_price": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "underperform": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "analyst": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/InstitutionRatingAnalyst"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "instratings": {},
-    "warnings": {
-      "items": {
-        "type": "string"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.10.2Aug 29, 2026

addedOutput schema / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"SymbolParam"
```

Changed13 schema fields changedv0.6.0Jun 26, 2026

removedOutput schema / $defs / InstitutionRatingAnalyst / description

Removed value: -"Analyst consensus block of `institution_rating`.\n\nSubset of documented fields; upstream may return more."

removedOutput schema / $defs / InstitutionRatingAnalyst / properties / buy / description
```
Removed value: -"Number of analysts rating \"buy\"."
```
removedOutput schema / $defs / InstitutionRatingAnalyst / properties / consensus_rating / description
```
Removed value: -"Consensus rating label."
```
removedOutput schema / $defs / InstitutionRatingAnalyst / properties / hold / description
```
Removed value: -"Number of analysts rating \"hold\"."
```
removedOutput schema / $defs / InstitutionRatingAnalyst / properties / outperform / description
```
Removed value: -"Number of analysts rating \"outperform\"."
```
removedOutput schema / $defs / InstitutionRatingAnalyst / properties / sell / description
```
Removed value: -"Number of analysts rating \"sell\"."
```
removedOutput schema / $defs / InstitutionRatingAnalyst / properties / target_price / description
```
Removed value: -"Consensus target price."
```
removedOutput schema / $defs / InstitutionRatingAnalyst / properties / underperform / description
```
Removed value: -"Number of analysts rating \"underperform\"."
```

removedOutput schema / $schema

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

removedOutput schema / description

Removed value: -"Returned by `institution_rating`.\n\nThe tool combines two upstream calls into\n`{\"analyst\": {...}, \"instratings\": [...]}`. Only the `analyst` fields are\ndocumented; the `instratings` payload shape is unspecified and left as raw\nJSON. Subset of documented fields; upstream may return more."

removedOutput schema / properties / analyst / description
```
Removed value: -"Analyst rating consensus summary."
```

removedOutput schema / properties / instratings / description

Removed value: -"Per-institution rating list. Shape is unspecified by the tool\ndescription; passed through as raw JSON."

removedOutput schema / title

Removed value: -"InstitutionRatingResponse"

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "InstitutionRatingAnalyst": {
+      "description": "Analyst consensus block of `institution_rating`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "buy": {
+          "description": "Number of analysts rating \"buy\".",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "consensus_rating": {
+          "description": "Consensus rating label.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "hold": {
+          "description": "Number of analysts rating \"hold\".",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "outperform": {
+          "description": "Number of analysts rating \"outperform\".",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "sell": {
+          "description": "Number of analysts rating \"sell\".",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "target_price": {
+          "description": "Consensus target price.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "underperform": {
+          "description": "Number of analysts rating \"underperform\".",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `institution_rating`.\n\nThe tool combines two upstream calls into\n`{\"analyst\": {...}, \"instratings\": [...]}`. Only the `analyst` fields are\ndocumented; the `instratings` payload shape is unspecified and left as raw\nJSON. Subset of documented fields; upstream may return more.",
+  "properties": {
+    "analyst": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/InstitutionRatingAnalyst"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Analyst rating consensus summary."
+    },
+    "instratings": {
+      "description": "Per-institution rating list. Shape is unspecified by the tool\ndescription; passed through as raw JSON."
+    }
+  },
+  "title": "InstitutionRatingResponse",
+  "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?

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds no behavioral context beyond the schema and annotations—nothing about return shape, data freshness, aggregation behavior, or rate limits. With such rich annotations, the bar is lower, but the description still contributes no additional behavioral transparency.

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 concise sentence with no filler or redundancy. It is front-loaded and immediately states the operation. No structural improvement is possible without adding substantive information.

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 is responsible for explaining what the tool returns beyond the vague phrase 'summary'. It does not specify whether the response contains aggregate counts, per-institution ratings, or a simple overall score. Given the complexity of the sibling group (institution_rating_detail, institution_rating_history, institution_rating_industry_rank), an agent could easily be confused about what data will be returned.

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 _jq and symbol are described in the input schema, including the important canonical-form note for symbol. The tool description itself adds no parameter-specific meaning, so the baseline of 3 applies because 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 states a specific verb ('Get') and a specific resource ('institution rating summary'), making the core purpose clear. It does not explicitly contrast with the many sibling tools (e.g., institution_rating_detail, institution_rating_history), but the word 'summary' does distinguish it from those variants, so it is more than a tautology.

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 choose this tool over alternatives such as institution_rating_detail or institution_rating_history. The description does not mention exclusions or prerequisites. The 'summary' wording only weakly implies a use case, so the agent receives essentially no routing help.

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

Deploy Server

Institution Rating

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools