Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Grid Order Detail

grid_detail
Read-only

Retrieve full details for a grid order: rule parameters, status, child orders, and lifecycle history. Use history_id and limit cursors to page through long histories.

Instructions

Full detail for one grid order: rule parameters, status, embedded child orders (grid_sub_orders) and lifecycle history (grid_order_history). Supports history_id cursor + limit paging.

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.
limitNoPage size for the embedded sub-order / history lists.
order_idYesGrid order ID.
history_idNoHistory cursor for paging the embedded trigger history.

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 / limit / format
      Removed value: -"int32"
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "expire_time": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "grid_order_history": {
-      "items": true,
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "grid_status": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "grid_sub_orders": {
-      "items": true,
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "lower_limit_price": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "order_id": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "settlement_currency": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "status": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "submitted_base_price": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "suspend_reason": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "symbol": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "upper_limit_price": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Addedv0.8.7

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description doesn't need to restate safety. It adds value by disclosing the response structure (embedded child orders and history lists) and the paging mechanism (history_id cursor + limit), which are behavioral details not present in 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?

Two sentences with the core purpose front-loaded and the paging note appended. No filler, every phrase contributes information.

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 detail tool with no output schema, the description conveys the operation, the response categories, and paging behavior. Minor gaps like default page size or whether history is included by default are not critical for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by clarifying that history_id acts as a cursor and limit controls page size, and by labeling the tool's scope as a single grid order. This adds meaningful semantic context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource ('one grid order') and enumerates the exact contents returned: rule parameters, status, embedded child orders, and lifecycle history. This clearly differentiates it from list-oriented siblings like grid_list and grid_list_by_ids.

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 phrase 'Full detail for one grid order' implies use when a single order's full context is needed, and the required order_id parameter reinforces that. However, it never explicitly contrasts with alternatives like grid_trigger_history or grid_list, nor states when not to use it.

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