Otto Intel

Prepare, submit, and recover an exact Base USDC exit

otto_delegation_exit

Destructive

Move an authenticated CDP end user's own Base USDC only through a server-held durable reservation. prepare returns one exact EIP-1559 transaction for client-side signing; the client must never broadcast it. submit validates and durably records the signed bytes and computed hash before the server broadcasts. status is read-only and cross-device. reconcile proves a canonical receipt without broadcasting, or returns the exact finalized sender+nonce replacement proof when another transaction consumed the reserved nonce. retry_same is explicit and can broadcast only the already-stored byte-identical transaction after reconciling first. cancel is accepted only before signed bytes were recorded. The caller presents Otto's delegation secret in x-otto-delegation-auth; user identity is always derived from accessToken.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`epoch`	No
`phase`	Yes
`state`	No
`account`	No
`receipt`	No
`user_id`	Yes
`has_exit`	Yes
`created_at`	No
`updated_at`	No
`destination`	No
`owner_token`	No
`replacement`	No
`transaction`	No
`operation_id`	No
`amount_atomic`	No
`lease_expires_at`	No
`transaction_hash`	No
`broadcast_attempts`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "account": {
+      "pattern": "^0x[0-9a-fA-F]{40}$",
+      "type": "string"
+    },
+    "amount_atomic": {
+      "pattern": "^[1-9][0-9]*$",
+      "type": "string"
+    },
+    "broadcast_attempts": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "created_at": {
+      "format": "date-time",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+      "type": "string"
+    },
+    "destination": {
+      "pattern": "^0x[0-9a-fA-F]{40}$",
+      "type": "string"
+    },
+    "epoch": {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    "has_exit": {
+      "type": "boolean"
+    },
+    "lease_expires_at": {
+      "format": "date-time",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+      "type": "string"
+    },
+    "operation_id": {
+      "format": "uuid",
+      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+      "type": "string"
+    },
+    "owner_token": {
+      "pattern": "^[0-9a-f]{64}$",
+      "type": "string"
+    },
+    "phase": {
+      "enum": [
+        "prepare",
+        "resume",
+        "submit",
+        "status",
+        "reconcile",
+        "retry_same",
+        "cancel"
+      ],
+      "type": "string"
+    },
+    "receipt": {
+      "additionalProperties": false,
+      "properties": {
+        "block_hash": {
+          "pattern": "^0x[0-9a-fA-F]{64}$",
+          "type": "string"
+        },
+        "block_number": {
+          "pattern": "^[1-9][0-9]*$",
+          "type": "string"
+        },
+        "status": {
+          "enum": [
+            "success",
+            "reverted"
+          ],
+          "type": "string"
+        },
+        "transaction_hash": {
+          "pattern": "^0x[0-9a-fA-F]{64}$",
+          "type": "string"
+        }
+      },
+      "required": [
+        "transaction_hash",
+        "block_number",
+        "block_hash",
+        "status"
+      ],
+      "type": "object"
+    },
+    "replacement": {
+      "additionalProperties": false,
+      "properties": {
+        "block_hash": {
+          "pattern": "^0x[0-9a-fA-F]{64}$",
+          "type": "string"
+        },
+        "block_number": {
+          "pattern": "^(?:0|[1-9][0-9]*)$",
+          "type": "string"
+        },
+        "finalized_head_block_hash": {
+          "pattern": "^0x[0-9a-fA-F]{64}$",
+          "type": "string"
+        },
+        "finalized_head_block_number": {
+          "pattern": "^(?:0|[1-9][0-9]*)$",
+          "type": "string"
+        },
+        "finalized_nonce": {
+          "pattern": "^[1-9][0-9]*$",
+          "type": "string"
+        },
+        "transaction_hash": {
+          "pattern": "^0x[0-9a-fA-F]{64}$",
+          "type": "string"
+        }
+      },
+      "required": [
+        "transaction_hash",
+        "block_number",
+        "block_hash",
+        "finalized_head_block_number",
+        "finalized_head_block_hash",
+        "finalized_nonce"
+      ],
+      "type": "object"
+    },
+    "state": {
+      "enum": [
+        "preparing",
+        "signing",
+        "signed",
+        "submitted",
+        "unknown",
+        "confirmed",
+        "reverted",
+        "replaced",
+        "canceled"
+      ],
+      "type": "string"
+    },
+    "transaction": {
+      "additionalProperties": false,
+      "properties": {
+        "chain_id": {
+          "const": 8453,
+          "type": "number"
+        },
+        "data": {
+          "pattern": "^0x(?:[0-9a-fA-F]{2})+$",
+          "type": "string"
+        },
+        "from": {
+          "pattern": "^0x[0-9a-fA-F]{40}$",
+          "type": "string"
+        },
+        "gas": {
+          "pattern": "^[1-9][0-9]*$",
+          "type": "string"
+        },
+        "max_fee_per_gas": {
+          "pattern": "^[1-9][0-9]*$",
+          "type": "string"
+        },
+        "max_priority_fee_per_gas": {
+          "pattern": "^(?:0|[1-9][0-9]*)$",
+          "type": "string"
+        },
+        "nonce": {
+          "pattern": "^(?:0|[1-9][0-9]*)$",
+          "type": "string"
+        },
+        "sign_idempotency_key": {
+          "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$",
+          "type": "string"
+        },
+        "to": {
+          "const": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
+          "type": "string"
+        },
+        "type": {
+          "const": "eip1559",
+          "type": "string"
+        },
+        "value": {
+          "const": "0",
+          "type": "string"
+        }
+      },
+      "required": [
+        "type",
+        "chain_id",
+        "nonce",
+        "from",
+        "to",
+        "value",
+        "data",
+        "gas",
+        "max_fee_per_gas",
+        "max_priority_fee_per_gas",
+        "sign_idempotency_key"
+      ],
+      "type": "object"
+    },
+    "transaction_hash": {
+      "pattern": "^0x[0-9a-fA-F]{64}$",
+      "type": "string"
+    },
+    "updated_at": {
+      "format": "date-time",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+      "type": "string"
+    },
+    "user_id": {
+      "pattern": "^[a-zA-Z0-9-]{1,100}$",
+      "type": "string"
+    }
+  },
+  "required": [
+    "phase",
+    "has_exit",
+    "user_id"
+  ],
+  "type": "object"
+}

AddedSep 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Even with destructiveHint already set, the description adds substantial behavioral detail: durable recording before broadcast, client never broadcasting the prepared transaction, cross-device read-only status, nonce-replacement proof behavior, and the delegation-auth/accessToken mechanism. There is no contradiction with the annotations.

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

Conciseness4/5

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

The description is dense but purposeful and front-loaded with the core purpose. Every sentence adds a real constraint or phase behavior; however, it is a single wall of text and would be easier to scan if the phases were structured as bullets or separate labeled paragraphs.

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 tool's complexity, the description covers auth, phase ordering, broadcast safety, cancel conditions, and nonce-conflict recovery, and an output schema exists so return values do not need to be enumerated. The main remaining gap is that it never explains how the caller selects among prepare/submit/status/reconcile/retry_same/cancel given the empty input schema.

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

Parameters4/5

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

The input schema defines zero parameters, so the 0-parameter baseline of 4 applies. The description adds useful invocation context by naming x-otto-delegation-auth and explaining that user identity comes from accessToken, even though no request payload or phase-selection parameter is documented.

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 clearly states the tool's purpose: moving an authenticated CDP end user's own Base USDC through a server-held durable reservation. It enumerates the exact workflow phases (prepare, submit, status, reconcile, retry_same, cancel), which distinguishes it from the broader delegation and prepare/swap siblings.

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

Usage Guidelines4/5

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

The description gives strong phase-specific usage context: prepare is client-side signing only and must never be broadcast, submit is the server broadcast point, reconcile handles nonce-conflict recovery, and cancel is only valid before signed bytes exist. It does not explicitly name alternative sibling tools, so it stops short of a 5.

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

All Otto Intel 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?