Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Business Segments History

business_segments_history
Read-onlyIdempotent

Retrieve historical business segment revenue trends by period and category to analyze segment performance and support investment decisions.

Instructions

Get historical business segment revenue trends (by period and category).

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.
cateNoSegment category filter
reportNoReport period: "qf" (quarterly), "saf" (semi-annual), "af" (annual)
symbolYesSecurity symbol, e.g. "AAPL.US"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "BusinessSegmentsHistoryPeriod": {
-      "properties": {
-        "business": {
-          "items": {
-            "$ref": "#/$defs/SegmentBreakdown"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        },
-        "currency": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "regionals": {
-          "items": {
-            "$ref": "#/$defs/SegmentBreakdown"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        },
-        "total": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "SegmentBreakdown": {
-      "properties": {
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "percent": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "value": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "historical": {
-      "items": {
-        "$ref": "#/$defs/BusinessSegmentsHistoryPeriod"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"BusinessSegmentsHistoryParam"
  4. Changed14 schema fields changedv0.6.0
    • removedOutput schema / $defs / BusinessSegmentsHistoryPeriod / description
      Removed value: -"One period snapshot in `business_segments_history`'s `historical`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / BusinessSegmentsHistoryPeriod / properties / business / description
      Removed value: -"Revenue by business line."
    • removedOutput schema / $defs / BusinessSegmentsHistoryPeriod / properties / currency / description
      Removed value: -"Settlement currency."
    • removedOutput schema / $defs / BusinessSegmentsHistoryPeriod / properties / date / description
      Removed value: -"Period date."
    • removedOutput schema / $defs / BusinessSegmentsHistoryPeriod / properties / regionals / description
      Removed value: -"Revenue by region."
    • removedOutput schema / $defs / BusinessSegmentsHistoryPeriod / properties / total / description
      Removed value: -"Total revenue for the period."
    • removedOutput schema / $defs / SegmentBreakdown / description
      Removed value: -"One segment breakdown entry in `business_segments_history`\n(`business[]` / `regionals[]`).\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / SegmentBreakdown / properties / name / description
      Removed value: -"Segment / region name."
    • removedOutput schema / $defs / SegmentBreakdown / properties / percent / description
      Removed value: -"Percentage of total."
    • removedOutput schema / $defs / SegmentBreakdown / properties / value / description
      Removed value: -"Absolute value."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `business_segments_history`. Wraps a `historical` array of\nper-period segment snapshots.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / historical / description
      Removed value: -"Per-period segment snapshots."
    • removedOutput schema / title
      Removed value: -"BusinessSegmentsHistoryResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "BusinessSegmentsHistoryPeriod": {
+      "description": "One period snapshot in `business_segments_history`'s `historical`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "business": {
+          "description": "Revenue by business line.",
+          "items": {
+            "$ref": "#/$defs/SegmentBreakdown"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "currency": {
+          "description": "Settlement currency.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "date": {
+          "description": "Period date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "regionals": {
+          "description": "Revenue by region.",
+          "items": {
+            "$ref": "#/$defs/SegmentBreakdown"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "total": {
+          "description": "Total revenue for the period.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "SegmentBreakdown": {
+      "description": "One segment breakdown entry in `business_segments_history`\n(`business[]` / `regionals[]`).\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "name": {
+          "description": "Segment / region name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "percent": {
+          "description": "Percentage of total.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "value": {
+          "description": "Absolute value.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `business_segments_history`. Wraps a `historical` array of\nper-period segment snapshots.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "historical": {
+      "description": "Per-period segment snapshots.",
+      "items": {
+        "$ref": "#/$defs/BusinessSegmentsHistoryPeriod"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "BusinessSegmentsHistoryResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. Addedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the 'trends' and period/category dimension, which is useful context beyond annotations. However, it doesn't disclose output structure or any edge cases, which is acceptable given the read-only nature but not exceptional.

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, front-loaded sentence that states the action and scope with no filler. It's efficient and easily parsed by an agent.

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?

Given the tool is a read-only getter with well-documented parameters and safety annotations, the description is sufficient for an agent to understand the tool's purpose. It hints at the return content ('revenue trends') without needing to detail the exact structure since there's no output schema. Minor gap: it doesn't clarify whether the response is a time series or single point, but the word 'trends' implies multiple periods.

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%, so all parameters are documented in the schema. The description's mention of 'by period and category' aligns with the report and cate parameters but doesn't add new meaning beyond the schema. Baseline 3 applies because the schema carries the parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 'historical business segment revenue trends', and adds 'by period and category' which distinguishes it from the sibling 'business_segments' tool. It's specific and unambiguous.

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 vs alternatives. The word 'historical' implies it's for historical data versus current, but it doesn't name the sibling tool or provide conditions. An agent would have to infer the use case.

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