DropEngine x402 Agent Services

scan_arbitrage

Paid Arbitrage Intelligence ($0.03 USDC). Compares Binance and Coinbase public spot order books at a requested trade size and applies caller- or server-configured taker fee assumptions. Rejects stale books. Excludes transfers, inventory rebalancing, and guaranteed execution; does not place orders.

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	Default
`asset`	Yes
`venues`	No
`quote_asset`	No	USDT
`trade_size_usd`	Yes
`fee_bps_by_venue`	No
`min_net_spread_bps`	No

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.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses price ($0.03 USDC), staleness handling ('rejects stale books'), and clear negative guarantees (no transfers, no inventory rebalancing, no guaranteed execution, does not place orders). It omits auth/credential requirements, rate limits, and what failure mode a rejected stale book produces for the caller.

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 paragraph is dense and front-loaded with cost and scope. The second paragraph is long generic routing boilerplate about Agent Action Gate, /api/discover, and workflows that has little to do with arbitrage scanning and inflates the definition considerably.

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

Completeness3/5

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

Because an output schema exists, return-value explanation is not required, and the scope/exclusions are well covered. However, for a 6-parameter paid tool with zero schema description coverage, the description leaves several inputs (min_net_spread_bps, quote_asset, venues) and the stale-book rejection behavior undefined for the caller.

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% across 6 parameters including a nested fee map, so the description must compensate. It explains trade_size ('at a requested trade size') and clarifies fee_bps_by_venue as 'caller- or server-configured', but says nothing about quote_asset, venues selection, or min_net_spread_bps threshold behavior.

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?

Opens with a specific verb+resource+scope: it compares Binance and Coinbase public spot order books at a requested trade size and applies taker fee assumptions. An agent can distinguish this from quote-style siblings like get_live_quote and from route_tool without opening the schema.

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 routing paragraph gives real guidance ('known single capability → call the direct tool', 'constrained comparison → use paid route_tool'), but it is ecosystem-wide boilerplate rather than advice about scan_arbitrage specifically. It never states when this tool beats get_live_quote or analyze_whale_activity for a given arbitrage question.

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?