x402 Agent Tollbooth

arbitrage_scan

Read-only

Cross-DEX Arbitrage & Liquidity Scanner. Analyzes Uniswap, Aerodrome, and BaseSwap pools for profitable routing opportunities. Cost: 0.002 USDC on Base & Solana (100% gasless).

Input Schema

Name	Required	Description	Default
`pair`	No	Token pair to scan, e.g. WETH/USDC
`chain`	No		base
`amount`	No	Human units of the first token, defaults to 1; exact raw units are derived from on-chain decimals
`slippage_bps`	No
`min_spread_bps`	No	Minimum spread in basis points

Output Schema

Name	Required	Description	Default
`limits`	No
`routes`	No
`status`	Yes
`service`	Yes
`endpoint`	Yes
`is_profitable`	No
`pairs_scanned`	No
`profitable_routes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 27, 2026

addedInput schema / properties / amount

Added value: +{
+  "description": "Human units of the first token, defaults to 1; exact raw units are derived from on-chain decimals",
+  "type": "string"
+}

addedInput schema / properties / chain

Added value: +{
+  "default": "base",
+  "enum": [
+    "base",
+    "solana"
+  ],
+  "type": "string"
+}

addedInput schema / properties / slippage_bps

Added value: +{
+  "default": 50,
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / is_profitable
```
Added value: +{
+  "type": "boolean"
+}
```
removedOutput schema / properties / latency_ms
```
Removed value: -{
-  "type": "integer"
-}
```
addedOutput schema / properties / limits
```
Added value: +{
+  "type": "array"
+}
```
removedOutput schema / properties / net_spread_bps
```
Removed value: -{
-  "type": "integer"
-}
```
addedOutput schema / properties / routes
```
Added value: +{
+  "type": "array"
+}
```
removedOutput schema / properties / top_route
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / verified_by
```
Removed value: -{
-  "type": "string"
-}
```

Changed1 schema field changedOct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "endpoint": {
+      "type": "string"
+    },
+    "latency_ms": {
+      "type": "integer"
+    },
+    "net_spread_bps": {
+      "type": "integer"
+    },
+    "pairs_scanned": {
+      "type": "integer"
+    },
+    "profitable_routes": {
+      "type": "integer"
+    },
+    "service": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "top_route": {
+      "type": "string"
+    },
+    "verified_by": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "service",
+    "endpoint"
+  ],
+  "type": "object"
+}

First observedOct 16, 2026

TDQS

B3.3/5.0

Behavior4/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 safety behavior is covered. The description adds useful context beyond annotations by disclosing the 0.002 USDC cost and that execution is gasless on Base and Solana, though it does not explain payment/auth mechanics or rate limits.

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 three short sentences with the core purpose front-loaded, followed by coverage and cost. Every sentence contributes useful information without waste.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. However, the description lacks usage guidance versus siblings and adds no parameter semantics, leaving moderate gaps for a five-parameter scanner.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain any of the five parameters, and schema description coverage is only 60%, leaving chain and slippage_bps without narrative descriptions. Since the description adds no parameter meaning beyond the schema, it does not compensate for the moderate coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: it analyzes Uniswap, Aerodrome, and BaseSwap pools for cross-DEX arbitrage and liquidity opportunities. It is clear what the tool does, though it does not explicitly differentiate itself from siblings like smart_router.

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 description implies the tool is for finding arbitrage opportunities, but it gives no explicit conditions for when to use it versus alternatives such as smart_router. There are no prerequisites, exclusions, or alternative-tool guidance.

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

All x402 Agent Tollbooth 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.