Nansen

Checking Smart Money DCA orders

smart_traders_and_funds_dcas

Read-only

Get Jupiter DCA (dollar-cost-averaging) orders opened by smart traders on Solana, including deposit size, amount spent so far and order status. Use this for scheduled accumulation intent; use smart_traders_and_funds_dex_trades for one-off swaps.

Input Schema

Name	Required	Description	Default
`request`	Yes	Request for smart money Jupiter DCA orders (v1 API, Solana only) - flattened.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 28, 2026

addedInput schema / properties / request / additionalProperties
```
Added value: +false
```

removedInput schema / properties / request / anyOf

Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "description": "Request for smart money Jupiter DCA orders (v1 API, Solana only) - flattened.",
-    "properties": {
-      "depositTokenAmount": {
-        "anyOf": [
-          {
-            "description": "Numeric range where from_value and to_value are optional,\nallowing for open-ended ranges (e.g., only minimum or only maximum).",
-            "properties": {
-              "from": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "default": null,
-                "description": "Minimum value (inclusive), optional"
-              },
-              "to": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "default": null,
-                "description": "Maximum value (inclusive), optional"
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Filter by deposited token amount"
-      },
-      "includeSmartMoneyLabels": {
-        "anyOf": [
-          {
-            "items": {
-              "enum": [
-                "30D Smart Trader",
-                "90D Smart Trader",
-                "180D Smart Trader",
-                "All Time Smart Trader",
-                "Fund",
-                "Smart HL Perps Trader",
-                "Any Smart Money"
-              ],
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Smart money category filters to include"
-      },
-      "inputTokenSymbol": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Filter by the token symbol being spent by the DCA order"
-      },
-      "orderBy": {
-        "anyOf": [
-          {
-            "enum": [
-              "dca_created_at",
-              "dca_updated_at",
-              "deposit_value_usd",
-              "deposit_token_amount",
-              "token_spent_amount",
-              "output_token_redeemed_amount"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Sort field. Pass an exact value above or None for default ('dca_created_at')."
-      },
-      "orderByDirection": {
-        "default": "DESC",
-        "description": "Sort direction: 'ASC' or 'DESC' (case-insensitive).",
-        "enum": [
-          "ASC",
-          "DESC",
-          "asc",
-          "desc"
-        ],
-        "type": "string"
-      },
-      "outputTokenSymbol": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Filter by the token symbol being accumulated by the DCA order"
-      },
-      "page": {
-        "default": 1,
-        "type": "integer"
-      },
-      "traderAddress": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Filter by trader address"
-      }
-    },
-    "type": "object"
-  }
-]

addedInput schema / properties / request / description

Added value: +"Request for smart money Jupiter DCA orders (v1 API, Solana only) - flattened."

addedInput schema / properties / request / properties

Added value: +{
+  "depositTokenAmount": {
+    "anyOf": [
+      {
+        "additionalProperties": false,
+        "description": "Numeric range where from_value and to_value are optional,\nallowing for open-ended ranges (e.g., only minimum or only maximum).",
+        "properties": {
+          "from": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null,
+            "description": "Minimum value (inclusive), optional"
+          },
+          "to": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null,
+            "description": "Maximum value (inclusive), optional"
+          }
+        },
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Filter by deposited token amount"
+  },
+  "includeSmartMoneyLabels": {
+    "anyOf": [
+      {
+        "items": {
+          "enum": [
+            "30D Smart Trader",
+            "90D Smart Trader",
+            "180D Smart Trader",
+            "All Time Smart Trader",
+            "Fund",
+            "Smart HL Perps Trader",
+            "Any Smart Money"
+          ],
+          "type": "string"
+        },
+        "type": "array"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Smart money category filters to include"
+  },
+  "inputTokenSymbol": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Filter by the token symbol being spent by the DCA order"
+  },
+  "orderBy": {
+    "anyOf": [
+      {
+        "enum": [
+          "dca_created_at",
+          "dca_updated_at",
+          "deposit_value_usd",
+          "deposit_token_amount",
+          "token_spent_amount",
+          "output_token_redeemed_amount"
+        ],
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Sort field. Pass an exact value above or None for default ('dca_created_at')."
+  },
+  "orderByDirection": {
+    "default": "DESC",
+    "description": "Sort direction: 'ASC' or 'DESC' (case-insensitive).",
+    "enum": [
+      "ASC",
+      "DESC",
+      "asc",
+      "desc"
+    ],
+    "type": "string"
+  },
+  "outputTokenSymbol": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Filter by the token symbol being accumulated by the DCA order"
+  },
+  "page": {
+    "default": 1,
+    "type": "integer"
+  },
+  "traderAddress": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Filter by trader address"
+  }
+}

addedInput schema / properties / request / type
```
Added value: +"object"
```

AddedSep 6, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the Solana-only scope and the kinds of data returned, but does not discuss pagination behavior, data freshness, or rate limits. With annotations covering the critical safety traits, a 3 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loads the tool's purpose, and then adds a crisp usage distinction. There is no redundant or wasted phrasing.

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?

Given the rich input schema, annotation coverage, and existing output schema, the description is complete enough for selection and invocation. The main missing context is how this differs from the sibling token_jup_dca tool and any pagination expectations, though the schema and tool prefix mitigate those gaps.

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%, and the nested request parameters are individually documented, so the schema already carries parameter semantics. The description does not explain filter behavior such as traderAddress, token symbol filters, numeric ranges, or smart-money label selection beyond the general 'opened by smart traders' phrasing. Baseline 3 is correct when the schema does the heavy lifting.

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 states a specific verb and resource: getting Jupiter DCA orders opened by smart traders on Solana. It also names the returned concepts (deposit size, amount spent, order status) and explicitly distinguishes the tool from smart_traders_and_funds_dex_trades.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance: 'Use this for scheduled accumulation intent.' It also names the relevant alternative and its condition: 'use smart_traders_and_funds_dex_trades for one-off swaps.' This is enough for an agent to choose between them without opening the schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nansen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?