Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Historical Orders

history_orders
Read-onlyIdempotent

Retrieve historical orders for a date range, excluding today, with optional symbol filter and pagination for US accounts.

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
_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.
end_atYesEnd time (RFC3339)
symbolNoFilter by symbol (optional)
us_pageNoUS accounts only: page number (default 1). Ignored for AP accounts (the region is inferred from the account — do not pass it).
start_atYesStart time (RFC3339)
us_limitNoUS accounts only: page size (default 20). Ignored for AP accounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / us_limit / format
      Removed value: -"int32"
    • removedInput schema / properties / us_page / format
      Removed value: -"int32"
  2. Changed3 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedInput schema / properties / us_limit / description
      Previous value: -"US accounts only, history_orders tool only: page size (default 20)."New value: +"US accounts only: page size (default 20). Ignored for\nAP accounts."
    • changedInput schema / properties / us_page / description
      Previous value: -"US accounts only, history_orders tool only: page number (default 1)."New value: +"US accounts only: page number (default 1). Ignored for\nAP accounts (the region is inferred from the account — do not pass it)."
  3. 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"
+}
  4. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"HistoryOrdersParam"
  5. Addedv0.4.5
  6. Removedv0.4.0
  7. Addedv0.3.2
  8. Removedv0.3.1
  9. First observedv0.1.12

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds meaningful behavioral details: it excludes today, returns a specific array structure, and explains regional pagination behavior (us_page/us_limit defaults, ignored for AP accounts). This goes beyond what annotations alone provide.

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 description is a single dense paragraph that front-loads the core purpose, then return format, then pagination details. It is efficient and every sentence adds necessary information, though it is somewhat packed with multiple clauses.

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?

Given there is no output schema, the description adequately provides the return structure. It covers pagination and regional differences, which are critical for correct usage. Minor omissions like error conditions or timezone assumptions are acceptable for a read-only query tool, and the annotations cover the safety profile.

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 baseline is 3. The description enhances parameter meaning by explaining pagination semantics (us_page default 1, us_limit default 20, ignored for AP accounts) and confirming RFC3339 format, which is not fully captured in the schema's terse descriptions.

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 verb and resource: 'Get historical orders between dates (excludes today)'. It also lists the exact return fields, making the tool's purpose unambiguous and distinct from siblings like today_orders and order_detail.

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 description implies usage context by excluding today (suggesting today_orders for current-day data) and notes US/AP pagination differences, but it does not explicitly name alternative tools or provide explicit when-not-to-use guidance. The exclusion of today is a clear context, but no sibling is referenced.

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