Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Get Grid Orders By IDs

grid_list_by_ids
Read-only

Fetch specific grid orders by their IDs to get detailed order information. Provide order IDs to retrieve selected grid orders from the longbridge server.

Instructions

Fetch specific grid orders by their IDs.

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.
order_idsYesGrid order IDs to fetch, e.g. ["123", "456"].

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: -{
-  "$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_orders": {
-      "items": {
-        "$ref": "#/$defs/GridOrderSummary"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "grid_orders"
-  ],
-  "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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the scoping detail of fetching specific IDs, but it does not describe response shape, ordering, or error behavior. With annotations covering the core behavioral traits, this is adequate 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, front-loaded sentence with no wasted words. The resource and selection criterion are immediately clear, and nothing extraneous is included.

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 ID-lookup tool with full schema coverage and safe annotations, the description provides enough context to invoke it correctly. No output schema exists, but the purpose clearly implies the return of the requested grid order objects.

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 baseline is 3. The description's 'by their IDs' merely echoes the order_ids parameter and adds no additional semantics beyond what the schema already documents. The _jq parameter is fully documented in 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 states a specific action ('Fetch') and resource ('specific grid orders') with a clear selection criterion ('by their IDs'). It is distinguishable from sibling tools like grid_list (all orders) and grid_detail (likely a single order), though it does not explicitly name them.

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 explicit guidance is given for when to use this tool versus alternatives such as grid_list or grid_detail. The ID-based selection is implied, but there are no stated exclusions, prerequisites, or comparisons to help an agent choose between related grid 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