Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

List DCA Plans

dca_list
Read-onlyIdempotent

Retrieve DCA recurring investment plans, filtering by status or symbol to narrow results.

Instructions

List DCA recurring investment plans. Filter by status (Active/Suspended/Finished) or symbol.

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.
pageNoPage number (default 1)
limitNoRecords per page (default 20)
statusNoFilter by status: Active, Suspended, Finished. Omit to return all.
symbolNoFilter by symbol, e.g. "AAPL.US". Omit to return all plans.

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 / limit / format
      Removed value: -"uint32"
    • removedInput schema / properties / page / format
      Removed value: -"uint32"
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "DcaPlan": {
-      "properties": {
-        "amount": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "currency": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "frequency": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "next_execution_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "plan_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "status": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "symbol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "plans": {
-      "items": {
-        "$ref": "#/$defs/DcaPlan"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"DcaListParam"
  4. Changed12 schema fields changedv0.6.0
    • removedOutput schema / $defs / DcaPlan / description
      Removed value: -"A single DCA recurring-investment plan."
    • removedOutput schema / $defs / DcaPlan / properties / amount / description
      Removed value: -"Amount invested per cycle (decimal string)."
    • removedOutput schema / $defs / DcaPlan / properties / currency / description
      Removed value: -"Settlement currency."
    • removedOutput schema / $defs / DcaPlan / properties / frequency / description
      Removed value: -"Investment frequency (Daily / Weekly / Monthly)."
    • removedOutput schema / $defs / DcaPlan / properties / next_execution_date / description
      Removed value: -"Next scheduled execution date (RFC3339; upstream `next_trd_date`)."
    • removedOutput schema / $defs / DcaPlan / properties / plan_id / description
      Removed value: -"Plan ID. Use with dca_update / dca_pause / dca_resume / dca_stop."
    • removedOutput schema / $defs / DcaPlan / properties / status / description
      Removed value: -"Plan status (Active / Suspended / Finished)."
    • removedOutput schema / $defs / DcaPlan / properties / symbol / description
      Removed value: -"Security symbol (e.g. \"AAPL.US\")."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `dca_list`. Upstream DCA plan-query payload forwarded after the\nstandard transform; the `next_trd_date` unix field is converted to RFC3339.\nSubset of the wire payload — only documented fields are declared; all\noptional."
    • removedOutput schema / properties / plans / description
      Removed value: -"Recurring-investment (DCA) plans."
    • removedOutput schema / title
      Removed value: -"DcaListResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "DcaPlan": {
+      "description": "A single DCA recurring-investment plan.",
+      "properties": {
+        "amount": {
+          "description": "Amount invested per cycle (decimal string).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "currency": {
+          "description": "Settlement currency.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "frequency": {
+          "description": "Investment frequency (Daily / Weekly / Monthly).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "next_execution_date": {
+          "description": "Next scheduled execution date (RFC3339; upstream `next_trd_date`).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "plan_id": {
+          "description": "Plan ID. Use with dca_update / dca_pause / dca_resume / dca_stop.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "description": "Plan status (Active / Suspended / Finished).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol": {
+          "description": "Security symbol (e.g. \"AAPL.US\").",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `dca_list`. Upstream DCA plan-query payload forwarded after the\nstandard transform; the `next_trd_date` unix field is converted to RFC3339.\nSubset of the wire payload — only documented fields are declared; all\noptional.",
+  "properties": {
+    "plans": {
+      "description": "Recurring-investment (DCA) plans.",
+      "items": {
+        "$ref": "#/$defs/DcaPlan"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "DcaListResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare this tool read-only, idempotent, and non-destructive. The description adds the filtering behavior and the resource scope, but it doesn't disclose additional behavioral details such as pagination behavior, response shape, or any operational constraints. With annotations covering the safety profile, the description makes a modest additive contribution, but not a rich one.

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, focused sentence that front-loads the core action ('List DCA recurring investment plans') and immediately covers the optional filters. Every word earns its place; no filler or redundant elaboration.

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 filtered list tool, the definition is nearly complete: the schema documents all five parameters with 100% coverage, annotations cover the safety profile, and the description states the purpose and filtering options. The only shortfall is that no output schema or return format is mentioned, but an agent can reasonably infer the return is a list of DCA plans.

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 description coverage is 100%, so the baseline is 3. The description does restate the status filter values and symbol filter concept, but those are already present in the schema. It adds no meaningful parameter semantics beyond the 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 uses a specific verb and resource: 'List DCA recurring investment plans', which clearly distinguishes it from DCA mutation tools like dca_create, dca_update, dca_stop, etc. It also states the filtering capabilities (by status or symbol), so an agent immediately knows what this tool offers.

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?

The description makes the usage context clear: call this when you need to list existing DCA plans, optionally filtered by status or symbol. However, it does not explicitly name alternatives such as dca_history or dca_stats, nor does it say when not to use it, so it stops short of full routing guidance.

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