longbridge

Official

by longbridge

Overview Schema Source Related Servers Score Discussions(1)Admin

Rust

Hybrid

DCA Execution History

dca_history

Read-onlyIdempotent

Retrieve execution history records for a DCA plan by plan ID, with optional pagination to view more or fewer records per page.

Instructions

Get execution history records for a DCA plan by plan_id.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (default 1)
`limit`	No	Records per page (default 20)
`plan_id`	Yes	Plan ID

Output Schema

TableJSON Schema

Name	Required	Description	Default
`executions`	No

Schema Changelog

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

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

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds no extra behavioral context, such as pagination behavior, rate limits, or data freshness. It minimally repeats the 'get' operation already implied by annotations.

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 concise sentence with no wasted words. However, it could include brief contextual detail without becoming verbose, hence not a 5.

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?

The tool is simple (fetch by plan_id) with full schema coverage and an output schema (not shown). The description is adequate for a read-only, idempotent retrieval. It lacks mention of pagination defaults but schema covers that.

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 parameters are fully documented in the schema. The description only mentions plan_id, missing page and limit. It adds no meaning beyond what the schema provides, meeting the baseline of 3.

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 the verb 'Get', the resource 'execution history records', and the scope 'by plan_id'. It effectively distinguishes from sibling DCA tools like dca_list (which lists plans) and dca_stats (statistics), making the tool's purpose unambiguous.

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 for retrieving history by plan_id but provides no explicit guidance on when to use this versus alternatives like dca_list or dca_stats. No when-not-to-use conditions or prerequisites are stated.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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