Skip to main content
Glama
longbridge

longbridge

Official

List DCA Plans

dca_list
Read-onlyIdempotent

List DCA recurring investment plans by status or symbol to track active, suspended, and finished schedules.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
plansNo

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: -"DcaListParam"
  2. 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"
  3. 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"
      +}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. First observedv0.1.12

TDQS

A4.5/5.0
Behavior5/5

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

Annotations fully cover behavioral aspects (readOnlyHint, idempotentHint, destructiveHint). The description adds value by specifying the resource and filtering, with no contradictions.

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?

Single sentence, front-loaded with verb and resource, includes essential filtering info without fluff.

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

Completeness5/5

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

With annotations and output schema present, the description provides sufficient context for a simple list tool: resource, filtering, and safe operation.

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 baseline is 3. The description repeats filter details already in schema, adding minimal extra meaning beyond summarizing status values and symbol.

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 action (List), resource (DCA recurring investment plans), and filtering options (status, symbol). It distinguishes from sibling tools like dca_create, dca_update, etc.

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 provides clear context for when to use the tool (listing plans) and filtering options. However, it does not explicitly state when not to use it or mention alternatives among sibling tools.

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