Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

Institutional Views

institutional_views
Read-onlyIdempotent

Fetch monthly institutional rating distribution timelines for any security, enabling analysis of analyst sentiment shifts.

Instructions

Get monthly institutional rating distribution timeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesSecurity symbol, e.g. "700.HK"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  2. Changed12 schema fields changedv0.6.0
    • removedOutput schema / $defs / InstitutionalViewsMonth / description
      Removed value: -"One month in `institutional_views`'s `months`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / InstitutionalViewsMonth / properties / buy / description
      Removed value: -"Buy count."
    • removedOutput schema / $defs / InstitutionalViewsMonth / properties / date / description
      Removed value: -"Month date (RFC3339; rewritten from a unix-epoch field)."
    • removedOutput schema / $defs / InstitutionalViewsMonth / properties / hold / description
      Removed value: -"Hold count."
    • removedOutput schema / $defs / InstitutionalViewsMonth / properties / outperform / description
      Removed value: -"Outperform count."
    • removedOutput schema / $defs / InstitutionalViewsMonth / properties / sell / description
      Removed value: -"Sell count."
    • removedOutput schema / $defs / InstitutionalViewsMonth / properties / total / description
      Removed value: -"Total ratings."
    • removedOutput schema / $defs / InstitutionalViewsMonth / properties / underperform / description
      Removed value: -"Underperform count."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `institutional_views`. Wraps a `months` array of monthly\nrating-distribution snapshots.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / months / description
      Removed value: -"Monthly rating-distribution snapshots."
    • removedOutput schema / title
      Removed value: -"InstitutionalViewsResponse"
  3. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "InstitutionalViewsMonth": {
+      "description": "One month in `institutional_views`'s `months`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "buy": {
+          "description": "Buy count.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "date": {
+          "description": "Month date (RFC3339; rewritten from a unix-epoch field).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "hold": {
+          "description": "Hold count.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "outperform": {
+          "description": "Outperform count.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "sell": {
+          "description": "Sell count.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "total": {
+          "description": "Total ratings.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "underperform": {
+          "description": "Underperform count.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `institutional_views`. Wraps a `months` array of monthly\nrating-distribution snapshots.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "months": {
+      "description": "Monthly rating-distribution snapshots.",
+      "items": {
+        "$ref": "#/$defs/InstitutionalViewsMonth"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "InstitutionalViewsResponse",
+  "type": "object"
+}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. Addedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare read-only and safe behavior. The description adds temporal granularity (monthly) and output type (distribution), but does not disclose data freshness, limits, or other behavioral traits beyond what annotations provide.

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?

A single, efficient sentence with no filler. It is front-loaded with the key action and resource.

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?

Given the tool's simplicity, an output schema exists, and annotations are present, the description is minimally adequate. However, it lacks differentiation from related sibling tools and could benefit from more context about what 'distribution' means.

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 coverage is 100% for the single parameter, which already has a clear description. The tool description adds no additional meaning for the parameter beyond the schema.

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 the tool retrieves a 'monthly institutional rating distribution timeline', specifying the verb and resource. However, it does not differentiate from sibling tools like institution_rating_history, which also deals with ratings over time.

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 explicit guidance on when to use this tool versus alternatives such as institution_rating or institution_rating_detail. The description lacks context about scenarios or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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