institution_ratingRetrieve a summary of institution ratings for a security symbol. Use this data to gauge market sentiment and inform investment decisions.
Get institution rating summary.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Security symbol, e.g. "700.HK" |
| Name | Required | Description | Default |
|---|---|---|---|
| analyst | No | ||
| warnings | No | ||
| instratings | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.10.2Output schema / properties / warningsAdded value: +{
+ "items": {
+ "type": "string"
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+}v0.7.1Input schema / titleRemoved value: -"SymbolParam"v0.6.0Output schema / $defs / InstitutionRatingAnalyst / descriptionRemoved value: -"Analyst consensus block of `institution_rating`.\n\nSubset of documented fields; upstream may return more."Output schema / $defs / InstitutionRatingAnalyst / properties / buy / descriptionRemoved value: -"Number of analysts rating \"buy\"."Output schema / $defs / InstitutionRatingAnalyst / properties / consensus_rating / descriptionRemoved value: -"Consensus rating label."Output schema / $defs / InstitutionRatingAnalyst / properties / hold / descriptionRemoved value: -"Number of analysts rating \"hold\"."Output schema / $defs / InstitutionRatingAnalyst / properties / outperform / descriptionRemoved value: -"Number of analysts rating \"outperform\"."Output schema / $defs / InstitutionRatingAnalyst / properties / sell / descriptionRemoved value: -"Number of analysts rating \"sell\"."Output schema / $defs / InstitutionRatingAnalyst / properties / target_price / descriptionRemoved value: -"Consensus target price."Output schema / $defs / InstitutionRatingAnalyst / properties / underperform / descriptionRemoved value: -"Number of analysts rating \"underperform\"."Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Output schema / descriptionRemoved 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."Output schema / properties / analyst / descriptionRemoved value: -"Analyst rating consensus summary."Output schema / properties / instratings / descriptionRemoved value: -"Per-institution rating list. Shape is unspecified by the tool\ndescription; passed through as raw JSON."Output schema / titleRemoved value: -"InstitutionRatingResponse"v0.5.6Output 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"
+}v0.4.5v0.4.0v0.3.2v0.3.1v0.1.12Does 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 and idempotency profile is well covered. The description's 'Get' aligns with those annotations but adds no additional behavioral context such as data freshness, rating sources, or summary composition. This is an acceptable baseline given the annotation coverage.
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 concise sentence with no filler or repetition, and the verb is front-loaded. It is appropriately sized for a simple read-only tool, though it could carry more useful detail about the rating summary without becoming bloated.
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?
For a one-parameter, read-only tool with a full input schema, an output schema, and strong annotations, the description is nearly sufficient for direct invocation. However, the ambiguity around what 'institution rating summary' means and how it differs from the several sibling rating tools leaves a modest completeness gap.
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?
Schema description coverage is 100%, and the single parameter symbol is already described in the schema with type and an example ('700.HK'). The description adds no parameter-level detail, but it does not need to compensate for missing schema information. This matches the baseline for high schema coverage.
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 uses a clear verb and resource: 'Get institution rating summary.' It is distinct enough from sibling tools like institution_rating_detail, institution_rating_history, and institution_rating_industry_rank through the word 'summary.' However, it does not specify what the summary contains, leaving some ambiguity about the exact rating scope.
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?
The description provides no guidance on when to use this tool versus alternatives. It does not mention institution_rating_detail, institution_rating_history, institution_rating_industry_rank, institutional_views, or consensus, and gives no exclusion conditions. An agent must infer the appropriate choice solely from the tool name and terse description.
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