Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Market Temperature

market_temperature
Read-onlyIdempotent

Check current market sentiment for HK, US, CN, or SG markets to gauge investor mood and guide decisions.

Instructions

Get current market sentiment temperature. market: HK/US/CN/SG.

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.
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: -{
-  "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"
-}New value: +null
  3. Changed1 schema field changedv0.8.7
    • addedOutput schema / properties / description
      Added value: +{
+  "type": "string"
+}
  4. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"MarketParam"
  5. Changed8 schema fields changedv0.6.0
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `market_temperature`."
    • removedOutput schema / properties / description
      Removed value: -{
-  "description": "Human-readable temperature description (locale-aware).",
-  "type": "string"
-}
    • removedOutput schema / properties / sentiment / description
      Removed value: -"Market sentiment indicator (0-100)."
    • removedOutput schema / properties / temperature / description
      Removed value: -"Temperature value (0-100)."
    • removedOutput schema / properties / timestamp / description
      Removed value: -"Snapshot timestamp (RFC3339)."
    • removedOutput schema / properties / valuation / description
      Removed value: -"Market valuation indicator (0-100)."
    • removedOutput schema / title
      Removed value: -"MarketTemperatureResponse"
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. However, the description adds no behavioral context beyond restating the purpose—no mention of output format, scale, or any side effects. Given the annotations, the bar is lower, but the description still fails to add any meaningful behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but it is under-specified. It front-loads the action but does not structure any additional useful context. It is concise but too brief to be genuinely helpful, balancing efficiency against completeness.

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

Completeness2/5

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

With no output schema, the description must explain what the tool returns, such as the scale or meaning of 'temperature'. It does not. The tool is simple, but an agent has no idea what the response looks like or how to interpret it. This is a significant gap for a tool that returns a sentiment metric.

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 the schema already documents the market parameter fully. The description repeats the accepted values ('HK/US/CN/SG') without adding new semantics like format, defaults, or examples. This meets the baseline of 3 but adds no value beyond the schema.

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 clearly states the action ('Get current market sentiment temperature') and identifies the resource (market sentiment temperature). It names the accepted market codes, distinguishing it from a historical variant (history_market_temperature) implicitly by 'current', but does not explicitly call out the sibling. Still, the purpose is 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 guidance on when to use this tool versus alternatives. It does not mention history_market_temperature or any other sentiment-related tool, nor any exclusions or preconditions. An agent must infer usage from the name alone.

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