Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

DCA Statistics

dca_stats
Read-onlyIdempotent

Retrieve DCA investment statistics for all plans or filter by symbol to analyze performance.

Instructions

Get DCA investment statistics.

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.
symbolNoFilter by symbol, e.g. "AAPL.US". Omit to return stats for all plans.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "DcaStatsItem": {
-      "properties": {
-        "invested": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "return_rate": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "symbol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "value": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "items": {
-      "items": {
-        "$ref": "#/$defs/DcaStatsItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "plan_count": {
-      "format": "int64",
-      "type": [
-        "integer",
-        "null"
-      ]
-    },
-    "return_rate": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "total_invested": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "total_return": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "total_value": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"DcaStatsParam"
  4. Changed14 schema fields changedv0.6.0
    • removedOutput schema / $defs / DcaStatsItem / description
      Removed value: -"Per-symbol DCA statistics line."
    • removedOutput schema / $defs / DcaStatsItem / properties / invested / description
      Removed value: -"Amount invested in this symbol (decimal string)."
    • removedOutput schema / $defs / DcaStatsItem / properties / return_rate / description
      Removed value: -"Return rate for this symbol (decimal string)."
    • removedOutput schema / $defs / DcaStatsItem / properties / symbol / description
      Removed value: -"Security symbol."
    • removedOutput schema / $defs / DcaStatsItem / properties / value / description
      Removed value: -"Current value of this symbol's position (decimal string)."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `dca_stats`. Aggregate DCA statistics forwarded after the\nstandard transform. Subset of the wire payload — only documented fields are\ndeclared; all optional."
    • removedOutput schema / properties / items / description
      Removed value: -"Per-symbol breakdown."
    • removedOutput schema / properties / plan_count / description
      Removed value: -"Number of plans included."
    • removedOutput schema / properties / return_rate / description
      Removed value: -"Overall return rate (decimal string)."
    • removedOutput schema / properties / total_invested / description
      Removed value: -"Total amount invested across plans (decimal string)."
    • removedOutput schema / properties / total_return / description
      Removed value: -"Total return (decimal string)."
    • removedOutput schema / properties / total_value / description
      Removed value: -"Current total market value (decimal string)."
    • removedOutput schema / title
      Removed value: -"DcaStatsResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "DcaStatsItem": {
+      "description": "Per-symbol DCA statistics line.",
+      "properties": {
+        "invested": {
+          "description": "Amount invested in this symbol (decimal string).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "return_rate": {
+          "description": "Return rate for this symbol (decimal string).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol": {
+          "description": "Security symbol.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "value": {
+          "description": "Current value of this symbol's position (decimal string).",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `dca_stats`. Aggregate DCA statistics forwarded after the\nstandard transform. Subset of the wire payload — only documented fields are\ndeclared; all optional.",
+  "properties": {
+    "items": {
+      "description": "Per-symbol breakdown.",
+      "items": {
+        "$ref": "#/$defs/DcaStatsItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "plan_count": {
+      "description": "Number of plans included.",
+      "format": "int64",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "return_rate": {
+      "description": "Overall return rate (decimal string).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total_invested": {
+      "description": "Total amount invested across plans (decimal string).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total_return": {
+      "description": "Total return (decimal string).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total_value": {
+      "description": "Current total market value (decimal string).",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "title": "DcaStatsResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

C2.8/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, read-only operation. The description adds no additional behavioral context, such as whether it returns aggregate data for all plans or per-plan, or if it requires authentication. With annotations covering safety, the lack of extra detail is acceptable but not exceptional.

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, short sentence—extremely concise. It's front-loaded with the verb 'Get' and the resource. While it lacks detail, it's not verbose. For a simple tool, this is acceptable, but it could be slightly more informative without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain what the response contains, but it doesn't. With 2 parameters and simple filters, the tool is not overly complex, but the lack of return type or example output means the agent doesn't know what 'statistics' means numerically. Sibling tools like dca_history likely provide detailed data, so a clearer distinction is needed. This is incomplete for an agent to call with confidence.

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 both parameters ('_jq' and 'symbol') are fully documented. The description doesn't add meaning beyond the schema; for instance, it doesn't clarify that 'symbol' filters by ticker and that omitting it returns all plans, which the schema already states. No value added beyond schema.

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

Purpose3/5

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

The description states the tool gets DCA investment statistics, but it's vague—it doesn't specify what kind of statistics (e.g., totals, performance, breakdowns) or the output format. It distinguishes from siblings like dca_list (listing plans) but doesn't clearly differentiate from dca_history (history of contributions) or trade_stats, which may overlap in concept. A more specific description like 'Get aggregated investment statistics for dollar-cost averaging plans' would be clearer.

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 gives no guidance on when to use this tool versus alternatives like dca_list, dca_history, or trade_stats. It doesn't state whether to use it for a summary vs. detailed history, or what filters apply. The agent must infer from the symbol parameter, but no explicit 'when to use' or 'when not to use' is provided.

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