institution_rating_historyRetrieve historical institution ratings for a security by submitting its symbol, such as 700.HK.
Get institution rating history.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Security symbol, e.g. "700.HK" |
| Name | Required | Description | Default |
|---|---|---|---|
| target_history | No | ||
| evaluate_history | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.7.1Input schema / titleRemoved value: -"SymbolParam"v0.6.0Output schema / $defs / EvaluateHistoryItem / descriptionRemoved value: -"One rating-evaluation change in `institution_rating_history`.\n\nSubset of documented fields; upstream may return more."Output schema / $defs / EvaluateHistoryItem / properties / date / descriptionRemoved value: -"Change date."Output schema / $defs / EvaluateHistoryItem / properties / firm / descriptionRemoved value: -"Issuing firm."Output schema / $defs / EvaluateHistoryItem / properties / new_rating / descriptionRemoved value: -"New rating."Output schema / $defs / EvaluateHistoryItem / properties / old_rating / descriptionRemoved value: -"Prior rating."Output schema / $defs / TargetHistoryItem / descriptionRemoved value: -"One target-price revision in `institution_rating_history`.\n\nSubset of documented fields; upstream may return more."Output schema / $defs / TargetHistoryItem / properties / analyst / descriptionRemoved value: -"Analyst name."Output schema / $defs / TargetHistoryItem / properties / date / descriptionRemoved value: -"Revision date."Output schema / $defs / TargetHistoryItem / properties / firm / descriptionRemoved value: -"Issuing firm."Output schema / $defs / TargetHistoryItem / properties / new_target / descriptionRemoved value: -"New target price."Output schema / $defs / TargetHistoryItem / properties / old_target / descriptionRemoved value: -"Prior target price."Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Output schema / descriptionRemoved 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."Output schema / properties / evaluate_history / descriptionRemoved value: -"Rating-evaluation changes."Output schema / properties / target_history / descriptionRemoved value: -"Target-price revisions."Output schema / titleRemoved value: -"InstitutionRatingHistoryResponse"v0.5.6Output 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"
+}v0.4.5v0.4.0v0.3.2v0.3.1v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, providing a strong safety profile. The description adds no further behavioral details (e.g., data range, ordering, pagination), but does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no extraneous information. Every word is necessary and functional.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema and comprehensive annotations, the description is adequate for a simple lookup tool. However, it does not explain what the history contains (e.g., time period, data fields), leaving some context unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage with a clear description for the 'symbol' parameter. The tool description adds no additional semantic meaning beyond what the schema provides, meeting the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves 'institution rating history', distinguishing it from sibling tools like 'institution_rating' (current) and 'institution_rating_detail' (detailed current). The purpose is direct and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any prerequisites or context. Usage is only implied by the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/longbridge/longbridge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server