Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Check DCA Support

dca_check
Read-onlyIdempotent

Check whether given security symbols support DCA recurring investment before setting up periodic buys.

Instructions

Check whether given symbols support DCA recurring investment.

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.
symbolsYesSecurity symbols to check, e.g. ["AAPL.US", "TSLA.US"]

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": {
-    "DcaCheckItem": {
-      "properties": {
-        "reason": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "support_dca": {
-          "type": [
-            "boolean",
-            "null"
-          ]
-        },
-        "symbol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "items": {
-      "items": {
-        "$ref": "#/$defs/DcaCheckItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"DcaCheckParam"
  4. Changed8 schema fields changedv0.6.0
    • removedOutput schema / $defs / DcaCheckItem / description
      Removed value: -"DCA-eligibility result for one symbol."
    • removedOutput schema / $defs / DcaCheckItem / properties / reason / description
      Removed value: -"Reason when unsupported."
    • removedOutput schema / $defs / DcaCheckItem / properties / support_dca / description
      Removed value: -"Whether the symbol supports DCA recurring investment."
    • removedOutput schema / $defs / DcaCheckItem / properties / symbol / description
      Removed value: -"Security symbol."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `dca_check`. DCA-eligibility result per queried symbol,\nforwarded after the standard transform (upstream `counter_ids` query →\nper-symbol items). Subset of the wire payload — only documented fields are\ndeclared; all optional."
    • removedOutput schema / properties / items / description
      Removed value: -"Per-symbol support results."
    • removedOutput schema / title
      Removed value: -"DcaCheckResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "DcaCheckItem": {
+      "description": "DCA-eligibility result for one symbol.",
+      "properties": {
+        "reason": {
+          "description": "Reason when unsupported.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "support_dca": {
+          "description": "Whether the symbol supports DCA recurring investment.",
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "symbol": {
+          "description": "Security symbol.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `dca_check`. DCA-eligibility result per queried symbol,\nforwarded after the standard transform (upstream `counter_ids` query →\nper-symbol items). Subset of the wire payload — only documented fields are\ndeclared; all optional.",
+  "properties": {
+    "items": {
+      "description": "Per-symbol support results.",
+      "items": {
+        "$ref": "#/$defs/DcaCheckItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "DcaCheckResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already convey readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the behavioral semantic that this is a support check, but does not disclose additional traits such as response format or any edge cases. Annotations cover the critical safety profile, so the description's contribution is modest.

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, complete sentence with no filler or redundant wording. The core purpose is front-loaded and immediately actionable.

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 read-only check tool with one required array parameter and no output schema, the description provides sufficient context for a correct call. The main minor gap is that the response shape is not described, but the simple nature of the check makes this acceptable without being fully explicit.

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 parameters are already fully documented. The description mentions 'given symbols', reinforcing the main parameter, but adds no new detail beyond the schema. Baseline 3 is appropriate.

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 ('check') and resource ('DCA recurring investment support') and clearly identifies the input ('given symbols'). It is easily distinguished from sibling DCA tools (dca_create, dca_update, dca_list, etc.) which perform management actions rather than eligibility checks.

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 does not explicitly state when to use this tool or provide alternatives, but the purpose is straightforward and the sibling dca_create implies a preflight use case (verify support before creating a DCA plan). Usage is implied rather than stated.

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