Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Grid Symbol Info

grid_symbol_info
Read-only

Retrieve pre-trade grid setup details for a security, including name, last price, lot sizes, price steps, and trading authorization info.

Instructions

Pre-trade grid setup info for a security (takes a symbol, not an order_id): security name, last price, board lot sizes (buy/sell), price-step (bid_size) table, and channel/authorization info (strategy grant flag, RTH support, supported s...

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".

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": {
-    "GridBidSizeRule": {
-      "properties": {
-        "bid_size": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "end_proceed": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "str_proceed": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "bid_sizes": {
-      "items": {
-        "$ref": "#/$defs/GridBidSizeRule"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "buy_lot_size": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "channel_info": {},
-    "last_done": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "lot_size": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "name": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "sell_lot_size": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Addedv0.8.7

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish read-only behavior; the description adds meaningful context by saying it returns channel/authorization info including strategy grant flag and RTH support, plus grid/board-lot parameters. No contradiction with readOnlyHint. The final clause is truncated, so it does not fully disclose all returned data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The visible portion is front-loaded: purpose, input distinction, and a compact list of return fields in one sentence. It earns high marks but not a 5 because the sentence trails off mid-word ('supported s...'), which reads as an incomplete definition if the truncation is literal.

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 single-required-parameter read-only tool with no output schema, the description gives enough information about return content (name, last price, lot sizes, price-step table, auth flags) to let an agent invoke it and understand the result. The truncated tail and absence of any response-format note keep it from being fully complete.

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 by emphasizing that the input is a security symbol and explicitly not an order_id, which prevents likely misuse with order-based grid tools. It does not add details for _jq, but the schema already documents that parameter fully.

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 opens with a specific resource and intent ('Pre-trade grid setup info for a security') and immediately disambiguates from order_id-based grid tools by saying it takes a symbol, not an order_id. It also lists concrete output contents, so an agent can tell exactly what this tool is for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description communicates the key input constraint ('takes a symbol, not an order_id') and frames the tool as pre-trade setup info, which tells an agent when to select it. It stops short of naming a concrete alternative tool or stating explicit when-not scenarios, so it is not a 5.

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