Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Operating Performance

operating
Read-onlyIdempotent

Get operating metrics for Hong Kong-listed stocks by symbol, such as 700.HK, to analyze key business performance data.

Instructions

Get company operating metrics (HK stocks only).

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.
symbolYesSecurity symbol, e.g. "700.HK". Use the canonical form — a padded code like "00700.HK" returns an empty record, not an error.

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."
    • changedInput schema / properties / symbol / description
      Previous value: -"Security symbol, e.g. \"700.HK\""New value: +"Security symbol, e.g. \"700.HK\". Use the canonical form — a padded code like \"00700.HK\" returns an empty record, not an error."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "OperatingItem": {
-      "properties": {
-        "metric_name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "period": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "unit": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "value": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "items": {
-      "items": {
-        "$ref": "#/$defs/OperatingItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  4. Changed9 schema fields changedv0.6.0
    • removedOutput schema / $defs / OperatingItem / description
      Removed value: -"One record in `operating`'s `items`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / OperatingItem / properties / metric_name / description
      Removed value: -"Metric name (e.g. passenger traffic, cargo volume)."
    • removedOutput schema / $defs / OperatingItem / properties / period / description
      Removed value: -"Reporting period."
    • removedOutput schema / $defs / OperatingItem / properties / unit / description
      Removed value: -"Unit of measure."
    • removedOutput schema / $defs / OperatingItem / properties / value / description
      Removed value: -"Metric value."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `operating`. Wraps an `items` array of operating metrics\n(HK stocks only).\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / items / description
      Removed value: -"Operating metric records."
    • removedOutput schema / title
      Removed value: -"OperatingResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "OperatingItem": {
+      "description": "One record in `operating`'s `items`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "metric_name": {
+          "description": "Metric name (e.g. passenger traffic, cargo volume).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "period": {
+          "description": "Reporting period.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "unit": {
+          "description": "Unit of measure.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "value": {
+          "description": "Metric value.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `operating`. Wraps an `items` array of operating metrics\n(HK stocks only).\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "items": {
+      "description": "Operating metric records.",
+      "items": {
+        "$ref": "#/$defs/OperatingItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "OperatingResponse",
+  "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.5/5.0
Behavior3/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. The description adds the meaningful HK-only scope constraint, but does not disclose output shape, pagination, or error behavior. The annotation coverage lowers the burden.

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?

A single sentence that front-loads the purpose and the key market restriction. No unnecessary words or repetition.

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

Completeness3/5

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

For a simple read-only tool with one required parameter and full schema coverage, it is mostly complete. However, with no output schema, the description could do more to clarify what 'operating metrics' actually includes to distinguish it from financial statements or segment data.

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%, with the symbol parameter already explaining canonical form and the empty-record behavior. The description adds no parameter-level detail beyond the schema, so the baseline score 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?

The description uses a specific verb and resource ('Get company operating metrics') and adds a clear market scope ('HK stocks only'). It is clear but does not explicitly differentiate from overlapping siblings like company or business_segments.

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 HK-only restriction provides a useful precondition, and the purpose implies when to use it. However, there is no explicit guidance about when to choose this tool over sibling tools that also cover company or financial performance data.

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