$AI on HyperEVM

Build Sell Transaction

ai_build_sell_tx

Read-onlyIdempotent

Build the unsigned transaction(s) to sell $AI: an approve first if allowance is insufficient, then the sell. Returns calldata only; the caller signs and sends.

Input Schema

TableJSON Schema

Name	Required	Description
`ai`	Yes	$AI amount to sell, decimal string, max 1000000000
`from`	Yes	0x seller address, required to check allowance and estimate gas
`slippage_bps`	No	Slippage tolerance in basis points, 0-5000, default 200

Output Schema

TableJSON Schema

Name	Required	Description	Default
`quote`	Yes
`steps`	Yes
`disclosure`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "disclosure": {
+      "type": "string"
+    },
+    "quote": {
+      "properties": {
+        "hypeOut": {
+          "type": "string"
+        },
+        "minHypeOut": {
+          "type": "string"
+        },
+        "slippageBps": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "hypeOut",
+        "minHypeOut",
+        "slippageBps"
+      ],
+      "type": "object"
+    },
+    "steps": {
+      "items": {
+        "properties": {
+          "note": {
+            "type": "string"
+          },
+          "step": {
+            "enum": [
+              "approve",
+              "sell"
+            ],
+            "type": "string"
+          },
+          "tx": {
+            "properties": {
+              "chainId": {
+                "type": "string"
+              },
+              "data": {
+                "type": "string"
+              },
+              "from": {
+                "type": "string"
+              },
+              "gas": {
+                "type": "string"
+              },
+              "to": {
+                "type": "string"
+              },
+              "value": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "chainId",
+              "to",
+              "value",
+              "data"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "step",
+          "tx"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "steps",
+    "quote",
+    "disclosure"
+  ],
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds behavioral context beyond the annotations: it returns calldata only and requires the caller to sign and send, and it handles an approve step if allowance is insufficient. This complements the readOnlyHint and idempotentHint without contradiction.

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 with no filler, front-loading the purpose and then the key behavioral notes. Every sentence earns its place.

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

Completeness5/5

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

For a tool that builds transactions with a clear output schema, the description covers the purpose, the return behavior, and the approve-sell logic. Nothing an agent needs to call it correctly is missing.

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?

The input schema covers all three parameters with descriptions (100% coverage), so the description does not need to add parameter details. It does not provide additional semantics beyond what the schema already states, so the baseline of 3 applies.

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 verb 'Build' and the resource 'unsigned transaction(s) to sell $AI', and distinguishes it from sibling tools like ai_build_buy_tx and quote tools. It specifies the approve-then-sell sequence, leaving no ambiguity about the tool's function.

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 implicitly conveys this is for building sell transactions and returning calldata for the caller to sign, but it does not explicitly name alternatives or conditions for when to use this over ai_quote_sell or ai_build_buy_tx. The context is clear but exclusions are absent.

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

All $AI on HyperEVM 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?