Skip to main content
Glama
longbridge

longbridge

Official

DCA Statistics

dca_stats
Read-onlyIdempotent

Retrieve dollar-cost averaging investment statistics. Filter by symbol to view plan-specific data, or omit to get stats for all plans.

Instructions

Get DCA investment statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoFilter by symbol, e.g. "AAPL.US". Omit to return stats for all plans.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNo
plan_countNo
return_rateNo
total_valueNo
total_returnNo
total_investedNo

Schema Changelog

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

  1. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"DcaStatsParam"
  2. 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"
  3. 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"
      +}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. 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 (readOnlyHint, idempotentHint, destructiveHint) clearly indicate it is a safe read operation. The description adds no further behavioral context, but the annotations shoulder the burden, so a neutral score is appropriate.

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 sentence with no wasted words. While it is concise, it could benefit from more detail without becoming verbose, so it earns a 4 for being efficiently minimal.

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?

The description is too minimal for a tool that likely returns complex statistics. Even though an output schema exists, the description should hint at the nature of 'statistics' (e.g., returns metrics like cost basis, returns, etc.) to help the agent judge usefulness.

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?

The input schema provides 100% coverage with a detailed description for the 'symbol' parameter. The tool description adds no additional meaning beyond what the schema already states, so baseline 3.

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 says 'Get DCA investment statistics,' which states a verb and resource, but it is vague given the numerous sibling DCA tools (dca_list, dca_history, dca_check, etc.). It does not specify what 'statistics' means or how it differs from other DCA endpoints.

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?

No guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent to guess the appropriate use case.

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

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