Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Institutional Views

institutional_views
Read-onlyIdempotent

Fetch monthly institutional rating distribution for a security symbol to observe analyst sentiment shifts over time. Track buy, hold, and sell rating trends.

Instructions

Get monthly institutional rating distribution timeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional 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.
symbolYesSecurity 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.

  1. Changed2 schema fields changedv0.12.0
    • 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."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "InstitutionalViewsMonth": {
-      "properties": {
-        "buy": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "hold": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "outperform": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "sell": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "total": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "underperform": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "months": {
-      "items": {
-        "$ref": "#/$defs/InstitutionalViewsMonth"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  4. 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"
  5. 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"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. Addedv0.3.0

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, so the description's 'Get' is consistent. However, the description adds no additional behavioral context such as the return format, time-series structure, pagination, or any limits. It relies entirely on annotations and does not enrich them with useful details.

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 redundant words, front-loading the core action and resource. It is appropriately short, though it sacrifices useful detail. For a simple get tool, this level of conciseness is acceptable, though more context could be added without becoming verbose.

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?

The tool is simple with one required parameter and no output schema, but the description is minimal. It does not explain what the 'distribution timeline' contains, how it differs from related institutional rating tools, or any caveats. Given the lack of output schema and the presence of several similar siblings, this is insufficient for an agent to correctly select and use it.

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?

The schema provides descriptions for both parameters (symbol and _jq) with 100% coverage, so the description adds nothing about parameters. The word 'monthly' refers to data granularity rather than parameter semantics. With high schema coverage, the baseline of 3 is appropriate; the description does not need to compensate.

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 verb 'Get' and the resource 'monthly institutional rating distribution timeline', which is specific and not a tautology. However, it does not differentiate this from closely related sibling tools like institution_rating_history or institution_rating, which likely have overlapping functionality. The purpose is clear but sibling distinction is missing.

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?

There is no guidance on when to use this tool versus alternatives such as institution_rating_history or institution_rating_industry_rank. The description provides no context for selection, leaving the agent to guess which tool is appropriate for a given request.

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

Deploy Server

Other Tools