Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Broker Queue

brokers
Read-onlyIdempotent

Retrieve broker queue for Hong Kong stocks and map broker IDs to participant names to identify trading activity.

Instructions

Get broker queue (HK stocks only). Map broker IDs to names via participants.

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": {
-    "BrokerLevel": {
-      "properties": {
-        "broker_ids": {
-          "items": {
-            "format": "int32",
-            "type": "integer"
-          },
-          "type": "array"
-        },
-        "position": {
-          "format": "int32",
-          "type": "integer"
-        }
-      },
-      "required": [
-        "position",
-        "broker_ids"
-      ],
-      "type": "object"
-    }
-  },
-  "properties": {
-    "ask_brokers": {
-      "items": {
-        "$ref": "#/$defs/BrokerLevel"
-      },
-      "type": "array"
-    },
-    "bid_brokers": {
-      "items": {
-        "$ref": "#/$defs/BrokerLevel"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "bid_brokers",
-    "ask_brokers"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  4. Changed7 schema fields changedv0.6.0
    • removedOutput schema / $defs / BrokerLevel / properties / broker_ids / description
      Removed value: -"Broker IDs queueing at this level. Map them to names via `participants`."
    • removedOutput schema / $defs / BrokerLevel / properties / position / description
      Removed value: -"Position number (1-based, depth ordering)."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `brokers`. Bid/ask broker queues for a security."
    • removedOutput schema / properties / ask_brokers / description
      Removed value: -"Ask brokers, best price first."
    • removedOutput schema / properties / bid_brokers / description
      Removed value: -"Bid brokers, best price first."
    • removedOutput schema / title
      Removed value: -"BrokersResponse"
  5. Addedv0.4.5
  6. Removedv0.4.0
  7. Addedv0.3.2
  8. Removedv0.3.1
  9. 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 cover the safety profile (readOnlyHint, idempotentHint, non-destructive), so the description's added behavioral value is limited to the market-scope constraint. It does not disclose response shape, ordering, or queue-specific behavior, though annotations lower 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?

Two terse sentences with the verb and resource front-loaded. The second sentence adds a meaningful resolution step rather than filler.

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, one-required-parameter tool, the description plus schema covers the essential calling contract. It doesn't describe the queue's return fields, but the participants reference tells the agent how to interpret broker IDs, which is the main interpretive gap.

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 `symbol` and `_jq` are already fully documented. The description adds no parameter-level detail; the baseline of 3 is appropriate.

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 names a specific resource ('broker queue') and a concrete action ('Get'), and narrows scope with 'HK stocks only'. It points to participants for ID resolution but does not explicitly contrast itself with related broker_holding* siblings.

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 stocks only' qualifier gives a clear scope for when this tool applies, and the participants hint suggests a supporting data source. However, there is no explicit when-not-to-use guidance or named alternatives among the many broker-related tools.

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