Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Historical Market Temperature

history_market_temperature
Read-onlyIdempotent

Retrieve historical market temperature time series for HK, US, CN, or SG markets over a specified date range to analyze past sentiment and market heat.

Instructions

Get historical market temperature time series.

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.
endYesEnd date (yyyy-mm-dd)
startYesStart date (yyyy-mm-dd)
marketYesMarket code: HK, US, CN, SG

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": {
-    "MarketTemperatureResponse": {
-      "properties": {
-        "description": {
-          "type": "string"
-        },
-        "sentiment": {
-          "format": "int32",
-          "type": "integer"
-        },
-        "temperature": {
-          "format": "int32",
-          "type": "integer"
-        },
-        "timestamp": {
-          "type": "string"
-        },
-        "valuation": {
-          "format": "int32",
-          "type": "integer"
-        }
-      },
-      "required": [
-        "temperature",
-        "description",
-        "valuation",
-        "sentiment",
-        "timestamp"
-      ],
-      "type": "object"
-    }
-  },
-  "properties": {
-    "list": {
-      "items": {
-        "$ref": "#/$defs/MarketTemperatureResponse"
-      },
-      "type": "array"
-    },
-    "type": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "type",
-    "list"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.8.7
    • addedOutput schema / $defs / MarketTemperatureResponse / properties / description
      Added value: +{
+  "type": "string"
+}
  4. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"MarketDateRangeParam"
  5. Changed11 schema fields changedv0.6.0
    • removedOutput schema / $defs / MarketTemperatureResponse / description
      Removed value: -"Returned by `market_temperature`."
    • removedOutput schema / $defs / MarketTemperatureResponse / properties / description
      Removed value: -{
-  "description": "Human-readable temperature description (locale-aware).",
-  "type": "string"
-}
    • removedOutput schema / $defs / MarketTemperatureResponse / properties / sentiment / description
      Removed value: -"Market sentiment indicator (0-100)."
    • removedOutput schema / $defs / MarketTemperatureResponse / properties / temperature / description
      Removed value: -"Temperature value (0-100)."
    • removedOutput schema / $defs / MarketTemperatureResponse / properties / timestamp / description
      Removed value: -"Snapshot timestamp (RFC3339)."
    • removedOutput schema / $defs / MarketTemperatureResponse / properties / valuation / description
      Removed value: -"Market valuation indicator (0-100)."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `history_market_temperature`."
    • removedOutput schema / properties / list / description
      Removed value: -"Per-period samples in chronological order."
    • removedOutput schema / properties / type / description
      Removed value: -"Granularity, e.g. \"day\"."
    • removedOutput schema / title
      Removed value: -"HistoryMarketTemperatureResponse"
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds that the result is a time series, but does not disclose granularity, output format, or edge cases. The annotation coverage lowers the burden, so the added value beyond annotations is modest.

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 with no filler. It front-loads the action and resource, and every word contributes to the core meaning.

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?

For a low-complexity, read-only tool with fully described parameters and helpful annotations, this description is largely sufficient for selection and invocation. It does not provide alternative routing or output details, but those are not essential for this simple time-series query.

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%, and the inputs (market, start, end, _jq) are already documented with types and format hints. The description adds no parameter-specific meaning, so the baseline 3 is appropriate.

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?

States a specific verb ('Get'), resource ('market temperature'), and scope ('historical time series'). The word 'historical' clearly differentiates this tool from the sibling market_temperature tool, and 'time series' clarifies the expected output shape.

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 only implies when the tool should be used: when historical market temperature data is needed. It does not explicitly mention alternatives such as market_temperature for current data, nor does it state exclusions or prerequisites.

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