Skip to main content
Glama
longbridge

longbridge

Official

List Grid Orders

grid_list
Read-only

List grid trading orders with filters for symbol, status, pagination, and sorting. Retrieve specific grid orders by criteria or get all orders for portfolio management.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
has_moreYes
grid_orderYes
Behavior4/5

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

Read-only behavior is consistent with annotations; description adds filter details without introducing side effects or contradictions.

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?

Single, clear sentence covering purpose and key filtering/pagination features without unnecessary verbosity.

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?

Sufficient for a list operation; output schema exists so return values need not be described. Could mention pagination behavior, but not essential.

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?

The input schema already includes full parameter descriptions with examples; the description repeats these without adding new meaning beyond the schema.

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?

Clearly states it lists grid trading orders, distinguishing it from detail or submission tools like grid_detail and grid_submit.

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?

Implies usage for retrieving lists with filters, but does not explicitly contrast with alternatives; adequate for a straightforward listing operation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/longbridge/longbridge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server