Nansen

Checking Jupiter DCA orders

token_jup_dca

Read-only

Get Jupiter DCA (dollar-cost-averaging) orders opened against a Solana token, with deposit size, amount spent so far, amount accumulated and order status. Use this to see scheduled buying or selling pressure that has not hit the market yet; use token_dex_trades for trades already executed. Solana tokens only.

Input Schema

Name	Required	Description	Default
`request`	Yes	Request for Jupiter DCA orders on a Solana token (flattened).

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 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 Jupiter DCA orders on a Solana token (flattened).",
-    "properties": {
-      "depositUsdValue": {
-        "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 USD value of the DCA deposit"
-      },
-      "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": "Restrict to traders holding these smart money labels"
-      },
-      "page": {
-        "default": 1,
-        "type": "integer"
-      },
-      "status": {
-        "anyOf": [
-          {
-            "enum": [
-              "Active",
-              "Closed"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Filter by DCA order status"
-      },
-      "tokenAddress": {
-        "description": "Token address on Solana",
-        "type": "string"
-      },
-      "traderAddress": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Filter by trader address"
-      }
-    },
-    "required": [
-      "tokenAddress"
-    ],
-    "type": "object"
-  }
-]

addedInput schema / properties / request / description

Added value: +"Request for Jupiter DCA orders on a Solana token (flattened)."

addedInput schema / properties / request / properties

Added value: +{
+  "depositUsdValue": {
+    "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 USD value of the DCA deposit"
+  },
+  "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": "Restrict to traders holding these smart money labels"
+  },
+  "page": {
+    "default": 1,
+    "type": "integer"
+  },
+  "status": {
+    "anyOf": [
+      {
+        "enum": [
+          "Active",
+          "Closed"
+        ],
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Filter by DCA order status"
+  },
+  "tokenAddress": {
+    "description": "Token address on Solana",
+    "type": "string"
+  },
+  "traderAddress": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Filter by trader address"
+  }
+}

addedInput schema / properties / request / required
```
Added value: +[
+  "tokenAddress"
+]
```
addedInput schema / properties / request / type
```
Added value: +"object"
```

AddedSep 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds the non-obvious chain restriction (Solana only) and clarifies that the data represents forward-looking, not-yet-executed pressure rather than historical fills, which prevents misinterpretation of the results.

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?

Two sentences, no filler. The core definition and returned fields come first, followed by the routing guidance and the chain constraint, so the most decision-relevant information is front-loaded.

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?

An output schema exists, so return values need no prose elaboration, and the description correctly spends its budget on scope and alternatives instead. The only gaps are minor: no mention of pagination behavior despite a page parameter, and no reference to the sibling smart_traders_and_funds_dcas variant.

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 every nested field — status enum, traderAddress, depositUsdValue range, smart-money labels, page — is documented in the schema itself. The description does not map its field mentions to filterable parameters or explain pagination, so it adds no semantic value beyond the schema, making the baseline 3 correct.

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 ('Get Jupiter DCA orders opened against a Solana token') and enumerates the returned fields (deposit size, amount spent, amount accumulated, status). It is immediately distinguishable from the adjacent token_dex_trades tool because it explicitly scopes itself to unexecuted, scheduled orders.

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 an explicit use case ('see scheduled buying or selling pressure that has not hit the market yet') and names the alternative for the complementary case ('use token_dex_trades for trades already executed'). It also states a hard boundary ('Solana tokens only'), leaving nothing to infer.

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?