Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Market Anomaly

anomaly
Read-onlyIdempotent

Detect unusual price and volume changes in HK, US, CN, and SG markets. Filter by specific stock symbol to view tailored anomaly alerts, up to 100 per request.

Instructions

Get market anomaly alerts (unusual price/volume changes). market: HK/US/CN/SG. symbol: optional, filter to a specific stock. count: results per page (default 50, max 100).

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.
countNoNumber of results to return (default: 50, max: 100)
marketYesMarket code: HK, US, CN, SG
symbolNoFilter to a specific symbol, e.g. "700.HK" or "AAPL.US"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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."
    • removedInput schema / properties / count / format
      Removed value: -"uint32"
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "AnomalyChange": {
-      "properties": {
-        "change_rate": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "symbol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "volume": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "all_off": {
-      "type": [
-        "boolean",
-        "null"
-      ]
-    },
-    "changes": {
-      "items": {
-        "$ref": "#/$defs/AnomalyChange"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"AnomalyParam"
  4. Changed9 schema fields changedv0.6.0
    • removedOutput schema / $defs / AnomalyChange / properties / change_rate / description
      Removed value: -"Price change rate (decimal ratio)."
    • removedOutput schema / $defs / AnomalyChange / properties / name / description
      Removed value: -"Display name of the security."
    • removedOutput schema / $defs / AnomalyChange / properties / symbol / description
      Removed value: -"Security symbol, e.g. \"700.HK\"."
    • removedOutput schema / $defs / AnomalyChange / properties / volume / description
      Removed value: -"Traded volume associated with the anomaly."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `anomaly`. Wraps a `changes` array of unusual price/volume\nalerts plus an `all_off` flag. Subset of the wire response — the\ndescription marks `changes[]` as having further undocumented fields."
    • removedOutput schema / properties / all_off / description
      Removed value: -"Whether anomaly alerting is globally off for the market."
    • removedOutput schema / properties / changes / description
      Removed value: -"Anomaly alert entries."
    • removedOutput schema / title
      Removed value: -"AnomalyResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "AnomalyChange": {
+      "properties": {
+        "change_rate": {
+          "description": "Price change rate (decimal ratio).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Display name of the security.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol": {
+          "description": "Security symbol, e.g. \"700.HK\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "volume": {
+          "description": "Traded volume associated with the anomaly.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `anomaly`. Wraps a `changes` array of unusual price/volume\nalerts plus an `all_off` flag. Subset of the wire response — the\ndescription marks `changes[]` as having further undocumented fields.",
+  "properties": {
+    "all_off": {
+      "description": "Whether anomaly alerting is globally off for the market.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "changes": {
+      "description": "Anomaly alert entries.",
+      "items": {
+        "$ref": "#/$defs/AnomalyChange"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "AnomalyResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already mark the call as read-only, idempotent, and non-destructive. The description adds context about alert content (unusual price/volume changes) and pagination defaults, but doesn't discuss result shape, update frequency, or ordering. No contradiction with annotations.

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 entire description is a single compact sentence with the action first, then the parameters and defaults. No filler or redundancy; every clause adds useful detail.

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 simple read-only lookup with one required parameter, the description plus schema and annotations is sufficient to invoke the tool correctly. It omits the output shape and any mention of no-result behavior, but this is minor given no output schema and the low complexity.

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 fully documents market, symbol, count, and _jq. The description largely repeats those meanings rather than adding new semantics, so the baseline of 3 applies.

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?

States a specific action ('Get market anomaly alerts') and clarifies the concept as unusual price/volume changes, with market scope. It doesn't explicitly name sibling tools like top_movers or market_status as alternatives, so it is clear but not strongly differentiated.

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 gives operational guidance — market is required, symbol optionally filters, count controls page size — but no explicit when-to-use versus alternatives or exclusions. The use case is implied by the purpose rather than stated as a decision rule.

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