Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

List Grid Orders

grid_list
Read-only

List grid trading orders filtered by symbol or status, with pagination and sorting options to review trading activity.

Instructions

List grid trading orders. Filter by symbol or comma-joined status (e.g. "Performing,Suspended"); supports page/limit and sort_by/sort_order.

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.
pageNoPage number (default 1).
limitNoRecords per page (default 20).
statusNoComma-joined status filter, e.g. "Performing,Suspended". Omit for all.
symbolNoFilter by symbol, e.g. "700.HK". Omit for all grid orders.
sort_byNoSort field (e.g. "created_at").
sort_orderNoSort order ("asc" / "desc").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / limit / format
      Removed value: -"int32"
    • removedInput schema / properties / page / format
      Removed value: -"int32"
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "GridOrderSummary": {
-      "properties": {
-        "created_at": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "grid_status": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "lower_limit_price": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "order_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "settlement_currency": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "status": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "stock_name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "submitted_base_price": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "symbol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "total_buy_quantity": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "total_profit_balance": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "total_sell_quantity": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "trigger_price_type": {
-          "format": "int32",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "upper_limit_price": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "grid_order": {
-      "items": {
-        "$ref": "#/$defs/GridOrderSummary"
-      },
-      "type": "array"
-    },
-    "has_more": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "grid_order",
-    "has_more"
-  ],
-  "type": "object"
-}New value: +null
  3. Addedv0.8.7

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful behavioral context around filtering by symbol or comma-joined status and supporting pagination/sorting, but it does not disclose response shape, default behavior beyond schema defaults, or any open-world caveats. This is acceptable but not rich.

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 front-loads the core purpose and then packs the meaningful capabilities into a compact, readable structure. There is no filler or redundant restating of the tool name.

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 read-only list tool with zero required parameters and fully documented schema fields, the description is nearly sufficient. It covers filters, pagination, and sorting, though it does not describe the output record shape and does not clarify the boundary with grid_list_by_ids.

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 coverage is 100%, so the schema already documents every parameter. The description repeats the comma-joined status example and mentions page/limit and sort fields, but adds little meaning beyond what the input schema already provides. Baseline 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 opens with a clear verb and resource: 'List grid trading orders.' It enumerates filtering, pagination, and sorting capabilities, making the operation unmistakable. It does not explicitly distinguish itself from the sibling grid_list_by_ids, so it stops short of a 5.

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 is given about when to prefer this tool over siblings such as grid_list_by_ids or grid_detail. The description implies a general listing use case but omits when-not-to-use scenarios and alternative routing, which matters given the large sibling set.

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