Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Forecast EPS

forecast_eps
Read-onlyIdempotent

Retrieve EPS forecast and analyst estimate history for a given security symbol to support investment analysis and valuation decisions.

Instructions

Get EPS forecast and analyst estimate history.

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": {
-    "ForecastEpsItem": {
-      "properties": {
-        "analyst_count": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "eps_actual": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "eps_estimate": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "forecast_end_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "forecast_start_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "surprise_pct": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "items": {
-      "items": {
-        "$ref": "#/$defs/ForecastEpsItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  4. Changed11 schema fields changedv0.6.0
    • removedOutput schema / $defs / ForecastEpsItem / description
      Removed value: -"One record in `forecast_eps`'s `items`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / ForecastEpsItem / properties / analyst_count / description
      Removed value: -"Number of contributing analysts."
    • removedOutput schema / $defs / ForecastEpsItem / properties / eps_actual / description
      Removed value: -"Actual reported EPS."
    • removedOutput schema / $defs / ForecastEpsItem / properties / eps_estimate / description
      Removed value: -"Consensus EPS estimate."
    • removedOutput schema / $defs / ForecastEpsItem / properties / forecast_end_date / description
      Removed value: -"Forecast period end (RFC3339; rewritten from a unix-epoch field)."
    • removedOutput schema / $defs / ForecastEpsItem / properties / forecast_start_date / description
      Removed value: -"Forecast period start (RFC3339; rewritten from a unix-epoch field)."
    • removedOutput schema / $defs / ForecastEpsItem / properties / surprise_pct / description
      Removed value: -"Surprise percentage (actual vs estimate)."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `forecast_eps`. Wraps an `items` array of EPS estimates.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / items / description
      Removed value: -"EPS forecast / actual records."
    • removedOutput schema / title
      Removed value: -"ForecastEpsResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "ForecastEpsItem": {
+      "description": "One record in `forecast_eps`'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_actual": {
+          "description": "Actual reported EPS.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "eps_estimate": {
+          "description": "Consensus EPS estimate.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "forecast_end_date": {
+          "description": "Forecast period end (RFC3339; rewritten from a unix-epoch field).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "forecast_start_date": {
+          "description": "Forecast period start (RFC3339; rewritten from a unix-epoch field).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "surprise_pct": {
+          "description": "Surprise percentage (actual vs estimate).",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `forecast_eps`. Wraps an `items` array of EPS estimates.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "items": {
+      "description": "EPS forecast / actual records.",
+      "items": {
+        "$ref": "#/$defs/ForecastEpsItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "ForecastEpsResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already provide a strong safety profile: readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds only the output scope and no behavioral details such as pagination, empty responses, or return shape. It does not contradict the annotations, but it also does not enrich them.

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?

The description is a single concise sentence with no filler: 'Get EPS forecast and analyst estimate history.' The core resource and action are front-loaded, and every word earns its place.

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?

For a read-only two-parameter query, the annotations and schema cover safety and inputs well. However, there is no output schema, and the description only vaguely mentions return categories without specifying fields, forecast period, or how estimates are structured. It is adequate but leaves meaningful gaps.

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 description coverage is 100%, with detailed parameter explanations including the canonical-symbol caveat for `symbol` and a full `_jq` description. The tool description itself contributes no additional parameter-level meaning, so the baseline of 3 is appropriate.

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 uses a clear verb and resource: 'Get EPS forecast and analyst estimate history.' It is unambiguous and distinct in topic, but it does not explicitly contrast sibling tools like consensus or institution_rating, so it stops short of full differentiation.

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?

The description gives no guidance on when to use this tool versus alternatives, and no exclusions or prerequisites are mentioned. With many related estimation/rating siblings present, selection would rely on the agent's prior knowledge rather than the description.

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