Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(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 market conditions.

Instructions

Get historical market temperature time series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesEnd date (yyyy-mm-dd)
startYesStart date (yyyy-mm-dd)
marketYesMarket code: HK, US, CN, SG

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
listYes
typeYes

Schema Changelog

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

  1. Changed1 schema field changedv0.8.7
    • addedOutput schema / $defs / MarketTemperatureResponse / properties / description
      Added value: +{
+  "type": "string"
+}
  2. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"MarketDateRangeParam"
  3. 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"
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. First observedv0.1.12

TDQS

C2.6/5.0
Behavior2/5

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

The description adds no behavioral context beyond the annotations (readOnlyHint, idempotentHint, etc.). It does not mention potential side effects, rate limits, or output format, so transparency is minimal.

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, direct sentence that immediately states the action and subject. It is concise, front-loaded, and contains no superfluous words.

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

Completeness1/5

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

The description is extremely minimal and does not explain what the market temperature time series represents, what units are used, or what the expected output looks like. With no output schema, this lack of context leaves the user with insufficient information to fully understand the tool's results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool description does not add any meaning to the parameters beyond the schema's own descriptions. Each parameter (start, end, market) already has a brief explanation in the schema, and the description offers no additional clarification or constraints.

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 market temperature time series', which accurately conveys the tool's purpose. It distinguishes from sibling tools like history_candlesticks or market_status by naming the specific data type.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. The description only states what it does, not when it should be chosen over other history or temperature-related 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