DropEngine x402 Agent Services

backtest_strategy

Paid Strategy Backtest ($0.10 USDC). Tests built-in long-only spot strategies against bounded public Binance OHLCV history. Signals form at candle close and execute at the next candle open. Applies configured fees/slippage; accepts declarative parameters only and never executes user code. Historical results are not predictions.

Agent entry points: risky external action → use Agent Action Gate when a combined action-specific safety assessment is needed; unclear capability/provider → use free /api/discover; constrained comparison between callable alternatives → use paid route_tool; known single capability → call the direct tool; multi-step objective → read the matching workflow recipe and call only relevant steps. Workflows are stateless recipes, not executors; calls are paid separately and are not bundle charged. Agent Action Gate does not approve payment, sign or broadcast transactions, evaluate seller reputation, replace transaction simulation, replace route_tool, or replace human approval.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`end`	Yes
`start`	Yes
`market`	Yes
`fee_bps`	No
`strategy`	Yes
`timeframe`	Yes
`slippage_bps`	No
`initial_capital`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	No
`next`	No
`tool`	Yes
`error`	No
`result`	No
`status`	No
`payment`	No
`success`	Yes
`agent_ux`	No
`timestamp`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 8, 2026

addedOutput schema / properties / agent_ux

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "meta": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "next": {
+      "items": {},
+      "type": "array"
+    },
+    "payment": {
+      "additionalProperties": false,
+      "properties": {
+        "execution_status": {
+          "enum": [
+            "not_started",
+            "succeeded",
+            "failed",
+            "unknown"
+          ],
+          "type": "string"
+        },
+        "status": {
+          "enum": [
+            "not_required",
+            "required",
+            "settled",
+            "failed",
+            "unknown"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "execution_status"
+      ],
+      "type": "object"
+    },
+    "result": {},
+    "status": {
+      "enum": [
+        "succeeded",
+        "failed",
+        "partial",
+        "outcome_unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "result",
+    "error",
+    "meta",
+    "payment",
+    "next"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / error

Added value: +{
+  "anyOf": [
+    {},
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / meta / additionalProperties
```
Previous value: -falseNew value: +{}
```

removedOutput schema / properties / meta / properties

Removed value: -{
-  "cache": {
-    "additionalProperties": false,
-    "properties": {
-      "age_ms": {
-        "minimum": 0,
-        "type": "number"
-      },
-      "hit": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "hit",
-      "age_ms"
-    ],
-    "type": "object"
-  },
-  "failed_sources": {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "reason": {
-          "type": "string"
-        },
-        "source": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "source",
-        "reason"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "latency_ms": {
-    "minimum": 0,
-    "type": "number"
-  },
-  "partial": {
-    "type": "boolean"
-  },
-  "sources": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-}

addedOutput schema / properties / meta / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / meta / required

Removed value: -[
-  "sources",
-  "latency_ms",
-  "partial",
-  "failed_sources",
-  "cache"
-]

addedOutput schema / properties / next

Added value: +{
+  "items": {},
+  "type": "array"
+}

addedOutput schema / properties / payment

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "execution_status": {
+      "enum": [
+        "not_started",
+        "succeeded",
+        "failed",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "not_required",
+        "required",
+        "settled",
+        "failed",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "execution_status"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / result
```
Added value: +{}
```

addedOutput schema / properties / status

Added value: +{
+  "enum": [
+    "succeeded",
+    "failed",
+    "partial",
+    "outcome_unknown"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "success",
-  "tool",
-  "timestamp",
-  "data",
-  "meta"
-]New value: +[
+  "success",
+  "tool",
+  "timestamp",
+  "data"
+]

First observedSep 28, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the $0.10 USDC cost, the signal-at-close/execute-at-next-open execution model, fee/slippage application, the safety guarantee that no user code runs, and the non-predictive nature of results. It stops short of rate limits, history-bound specifics, or failure modes, but this is strong disclosure for an unannotated mutation-style tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The first block is tight and front-loaded with the core operation, cost, and semantics. However, the large 'Agent entry points' paragraph is generic cross-server boilerplate repeated verbatim, adding bulk that does not earn its place for this specific tool.

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 not be described, and the description covers cost, execution semantics, constraints, and safety. The main gap is the polymorphic strategy object and market/capital parameters, which are not explained anywhere, but the definition is otherwise complete for calling the tool correctly.

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 0%, so the description must compensate. It adds meaning for fees/slippage ('configured fees/slippage'), the strategy nature ('built-in long-only spot strategies'), and the time-range/history bound, but leaves 'market' and 'initial_capital' unexplained and gives no detail on the strategy.parameters object. Partial compensation only.

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?

States a specific verb (backtest) and resource (strategy) with precise scope: built-in long-only spot strategies against bounded Binance OHLCV history. The 'never executes user code' and 'historical results are not predictions' clauses further pin down exactly what class of operation this is, distinguishing it from any code-execution or live-trading sibling.

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?

The 'Agent entry points' block is server-wide boilerplate (Agent Action Gate, /api/discover, route_tool, workflow recipes) that is not specific to backtest_strategy and offers no guidance on when to pick this tool versus an alternative. It only vaguely implies 'known single capability → call the direct tool.' No exclusions or preconditions for backtesting are given.

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

All DropEngine x402 Agent Services 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?