Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

Historical Orders

history_orders
Read-onlyIdempotent

Retrieve historical orders between specified dates, excluding today, to review past trading activity. Returns order details like symbol, side, status, quantity, price, and submission time.

Instructions

Get historical orders between dates (excludes today). Returns orders[]{order_id, symbol, side, status, quantity, price, submitted_at}. start_at/end_at in RFC3339. US accounts only: us_page, us_limit paginate via a separate US order endpoint (default page size 20 — pass us_page to see more than the first page).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_atYesEnd time (RFC3339)
symbolNoFilter by symbol (optional)
us_pageNoUS accounts only, history_orders tool only: page number (default 1).
start_atYesStart time (RFC3339)
us_limitNoUS accounts only, history_orders tool only: page size (default 20).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.8.4
    • addedInput schema / properties / us_limit
      Added value: +{
+  "description": "US accounts only, history_orders tool only: page size (default 20).",
+  "format": "int32",
+  "type": "integer"
+}
    • addedInput schema / properties / us_page
      Added value: +{
+  "description": "US accounts only, history_orders tool only: page number (default 1).",
+  "format": "int32",
+  "type": "integer"
+}
  2. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"HistoryOrdersParam"
  3. Addedv0.4.5
  4. Removedv0.4.0
  5. Addedv0.3.2
  6. Removedv0.3.1
  7. First observedv0.1.12

TDQS

A4.8/5.0
Behavior5/5

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

Adds important behavioral details beyond annotations: excludes today, lists exact return fields, and describes pagination via a separate endpoint. No contradictions with 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?

Three front-loaded sentences with no waste. Purpose, return shape, and pagination details each earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 params and no output schema, the description fully covers return fields, required parameters, and US-specific pagination. No gaps given the tool's complexity.

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

Parameters5/5

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

Schema coverage is 100%, but description adds significant meaning: explains RFC3339 format, clarifies us_page/us_limit pagination behavior (separate endpoint, default size), and states US-only restriction not in 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?

The description clearly states it gets historical orders between dates, excludes today, and lists return fields. It implicitly distinguishes from 'today_orders' and other order-related tools.

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?

Specifies US accounts only and explains pagination behavior. Provides clear context for when to use (historical period) but does not explicitly compare to sibling tools like 'today_orders'.

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