Skip to main content
Glama
longbridge

longbridge

Official

Business Segments History

business_segments_history
Read-onlyIdempotent

Retrieve historical revenue by business segment and period to analyze segment performance trends over time.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cateNoSegment category filter
reportNoReport period: "qf" (quarterly), "saf" (semi-annual), "af" (annual)
symbolYesSecurity symbol, e.g. "AAPL.US"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
historicalNo

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: -"BusinessSegmentsHistoryParam"
  2. 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"
  3. 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"
      +}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. Addedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds historical context but no additional behavioral traits beyond what annotations cover.

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 sentence of 8 words, front-loaded with key information, and contains no superfluous content.

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 low complexity, 3 parameters, and presence of output schema and annotations, the description is adequate but lacks differentiation from sibling tools like 'business_segments'.

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% with descriptions for all parameters. The description mentions 'period' and 'category' which map to 'report' and 'cate', but adds no extra meaning beyond the schema.

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 specifies grouping 'by period and category'. It effectively distinguishes from the sibling 'business_segments' which implies current data.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The description implies historical context, but does not mention alternatives or exclusions relative to sibling tools.

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