Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

Analyst Consensus

consensus
Read-onlyIdempotent

Retrieve financial consensus estimates for upcoming periods using a security symbol. Get analyst expectations for US and HK markets.

Instructions

Get financial consensus estimates for upcoming periods. US accounts querying a .US symbol get a differently-shaped response not matching output_schema (ai_summary plus a details[] list per period); other combinations match output_schema.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
listNo
itemsNo
reportNo
currencyNo
ai_summaryNo
opt_reportsNo

Schema Changelog

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

  1. Changed7 schema fields changedv0.8.4
    • addedOutput schema / $defs / UsConsensusEstimate
      Added value: +{
+  "properties": {
+    "actual": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "estimate": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / $defs / UsConsensusPeriod
      Added value: +{
+  "properties": {
+    "ebit": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/UsConsensusEstimate"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "eps": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/UsConsensusEstimate"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "fiscal_year": {
+      "format": "int32",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "report_txt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "revenue": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/UsConsensusEstimate"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / ai_summary
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / currency
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / list
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/UsConsensusPeriod"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}
    • addedOutput schema / properties / opt_reports
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}
    • addedOutput schema / properties / report
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  3. Changed11 schema fields changedv0.6.0
    • removedOutput schema / $defs / ConsensusItem / description
      Removed value: -"One record in `consensus`'s `items`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / ConsensusItem / properties / analyst_count / description
      Removed value: -"Number of contributing analysts."
    • removedOutput schema / $defs / ConsensusItem / properties / eps_estimate / description
      Removed value: -"EPS estimate."
    • removedOutput schema / $defs / ConsensusItem / properties / last_updated / description
      Removed value: -"Last update time."
    • removedOutput schema / $defs / ConsensusItem / properties / net_income_estimate / description
      Removed value: -"Net income estimate."
    • removedOutput schema / $defs / ConsensusItem / properties / period / description
      Removed value: -"Estimate period."
    • removedOutput schema / $defs / ConsensusItem / properties / revenue_estimate / description
      Removed value: -"Revenue estimate."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `consensus`. Wraps an `items` array of consensus estimates.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / items / description
      Removed value: -"Consensus estimate records for upcoming periods."
    • removedOutput schema / title
      Removed value: -"ConsensusResponse"
  4. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "ConsensusItem": {
+      "description": "One record in `consensus`'s `items`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "analyst_count": {
+          "description": "Number of contributing analysts.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "eps_estimate": {
+          "description": "EPS estimate.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "last_updated": {
+          "description": "Last update time.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "net_income_estimate": {
+          "description": "Net income estimate.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "period": {
+          "description": "Estimate period.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "revenue_estimate": {
+          "description": "Revenue estimate.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `consensus`. Wraps an `items` array of consensus estimates.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "items": {
+      "description": "Consensus estimate records for upcoming periods.",
+      "items": {
+        "$ref": "#/$defs/ConsensusItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "ConsensusResponse",
+  "type": "object"
+}
  5. Addedv0.4.5
  6. Removedv0.4.0
  7. Addedv0.3.2
  8. Removedv0.3.1
  9. First observedv0.1.12

TDQS

A3.8/5.0
Behavior4/5

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

Beyond annotations (readOnly, idempotent), the description discloses a critical behavioral trait: the response may not match the output schema for US accounts querying .US symbols, adding valuable context for the agent.

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?

Two sentences with no wasted words: the first states the core function, the second addresses a critical edge case. Front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, response shape inconsistency, and references the output schema. It lacks elaboration on what 'consensus estimates' includes (e.g., metrics, timeframes), but the output schema likely fills that gap.

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 single parameter 'symbol' is fully described in the schema. The description adds no new meaning about the parameter itself, but it does tie symbol usage to response shape, which is a behavioral nuance rather than semantic expansion.

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 it retrieves financial consensus estimates for upcoming periods. However, it does not distinguish from similar sibling tools like forecast_eps or institutional_views, so it lacks explicit differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for fetching consensus estimates but provides no guidance on when to use this tool versus alternatives. It notes a response shape difference for US accounts with .US symbols but does not suggest exclusions or preferred scenarios.

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