longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

DCA Execution History

dca_history

Read-onlyIdempotent

Retrieve execution history records for a dollar-cost averaging plan by plan ID. Supports pagination to browse through records.

Instructions

Get execution history records for a DCA plan by plan_id.

Input Schema

TableJSON Schema

Name	Required	Description
`_jq`	No	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.
`page`	No	Page number (default 1)
`limit`	No	Records per page (default 20)
`plan_id`	Yes	Plan ID

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.12.0Sep 23, 2026

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 / limit / format
```
Removed value: -"uint32"
```
removedInput schema / properties / page / format
```
Removed value: -"uint32"
```

Changed2 schema fields changedv0.10.6Sep 10, 2026

addedInput schema / properties / _jq
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "DcaExecution": {
-      "properties": {
-        "amount": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "order_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "price": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "quantity": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "status": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "executions": {
-      "items": {
-        "$ref": "#/$defs/DcaExecution"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"DcaHistoryParam"
```
Changed11 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / DcaExecution / description
```
Removed value: -"A single DCA plan execution record."
```
- removedOutput schema / $defs / DcaExecution / properties / amount / description
```
Removed value: -"Amount invested (decimal string)."
```
- removedOutput schema / $defs / DcaExecution / properties / date / description
```
Removed value: -"Execution date."
```
- removedOutput schema / $defs / DcaExecution / properties / order_id / description
```
Removed value: -"Resulting order ID, if any."
```
- removedOutput schema / $defs / DcaExecution / properties / price / description
```
Removed value: -"Execution price (decimal string)."
```
- removedOutput schema / $defs / DcaExecution / properties / quantity / description
```
Removed value: -"Quantity acquired (decimal string)."
```
- removedOutput schema / $defs / DcaExecution / properties / status / description
```
Removed value: -"Execution status."
```
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / description
```
Removed value: -"Returned by `dca_history`. Execution records for one DCA plan, forwarded\nafter the standard transform. Subset of the wire payload — only documented\nfields are declared; all optional."
```
- removedOutput schema / properties / executions / description
```
Removed value: -"Execution records."
```
- removedOutput schema / title
```
Removed value: -"DcaHistoryResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "DcaExecution": {
+      "description": "A single DCA plan execution record.",
+      "properties": {
+        "amount": {
+          "description": "Amount invested (decimal string).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "date": {
+          "description": "Execution date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "order_id": {
+          "description": "Resulting order ID, if any.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "price": {
+          "description": "Execution price (decimal string).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "quantity": {
+          "description": "Quantity acquired (decimal string).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "description": "Execution status.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `dca_history`. Execution records for one DCA plan, forwarded\nafter the standard transform. Subset of the wire payload — only documented\nfields are declared; all optional.",
+  "properties": {
+    "executions": {
+      "description": "Execution records.",
+      "items": {
+        "$ref": "#/$defs/DcaExecution"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "DcaHistoryResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
First observedv0.1.12May 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds the scoping constraint 'by plan_id' as useful context, but it does not disclose response format, pagination behavior, or error characteristics. This is adequate but not rich.

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?

A single, front-loaded sentence that states exactly what the tool does and its required input. There is no redundant wording or filler; every word earns its place.

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 simple read-only getter, the description plus the fully documented schema and safety annotations are nearly sufficient: plan_id is required and page/limit defaults are in the schema. The main gap is the lack of an output schema or a note about what fields the execution records contain, but this is a minor omission for such a straightforward tool.

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?

Schema coverage is 100%, so the schema fully documents all four parameters. The description only restates the plan_id role and adds no extra meaning for page, limit, or _jq, so it neither harms nor enhances the schema's baseline.

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 names a specific verb ('Get'), a clear resource ('execution history records'), and the key scope ('for a DCA plan by plan_id'). This is specific enough to separate dca_history from sibling tools like dca_list or dca_stats without ambiguity.

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

Usage Guidelines2/5

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

The description tells what the tool does but gives no guidance on when to prefer it over alternatives such as dca_stats or history_executions, and names no exclusions or prerequisites beyond plan_id. Usage is only implied, not stated.

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

Deploy Server

DCA Execution History

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools