Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Historical Executions

history_executions
Read-onlyIdempotent

Retrieve every trade execution in a date range, auto-paginated to return the complete fill history without truncation. Use trade_id as the stable dedupe key for accurate reconciliation.

Instructions

Get every trade execution (fill) in a date range, filtered by execution time (trade_done_at) and auto-paginated to return the complete set (never truncated at the 1000-per-page cap). Returns executions[]{order_id, trade_id, symbol, side, quantity, price, trade_done_at}; trade_id is the stable dedupe key. start_at/end_at in RFC3339.

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/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the bar is lower. The description adds valuable behavioral context beyond annotations: auto-pagination guarantees the complete set, filtering is by execution time, and trade_id is the stable dedupe key—information an agent could not infer from the schema.

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 compact sentences front-load the core behavior, then cover return shape, dedupe semantics, and time format. Every sentence earns its place, and no schema information is redundantly repeated.

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 no output schema, the description appropriately documents the return shape (executions array and key fields), the dedupe semantics, and pagination guarantee. Combined with annotations covering safety and a fully documented input schema, there is enough information for an agent to select and invoke the tool correctly.

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 description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by clarifying that start_at/end_at filter on trade_done_at, that the result is auto-paginated rather than manually paged, and that trade_id serves as the dedupe key—useful semantics not present in the parameter descriptions.

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

Purpose4/5

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

The description clearly identifies the resource (trade executions/fills), the action (get every execution in a date range), and adds meaningful scope details like filtering by trade_done_at and auto-pagination. It does not explicitly name a sibling alternative, but 'every...date range' plus the 'history_' prefix separates it well from tools like today_executions or trades.

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 makes the use case clear: retrieving the complete set of historical fills in a date range without truncation. However, it never explicitly says when not to use this tool or names alternatives for related needs (e.g., today_executions, order_detail), leaving routing between siblings to the agent's inference.

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