r0x-os

Construct a transfer

send

Construct an unsigned ETH or USDG transfer transaction on Robinhood Chain for a $0.01 USDG fee, ready to broadcast.

Instructions

Constructs an unsigned ETH or USDG transfer transaction on Robinhood Chain. Costs $0.01 USDG. Pass the result to the broadcast tool to actually sign and send it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "<to>",
      "amount": "<amount>",
      "token": "<token>"
    },
    "name": "send"
  }
}

Input Schema

Name	Required	Description
`to`	Yes
`token`	Yes
`amount`	Yes	Amount as a decimal string, e.g. "1.5"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It transparently states that the transaction is unsigned, that it costs $0.01 USDG, and that broadcasting is required to send—critical behavioral traits. It does not, however, describe the return format or error conditions, which would have made it fully transparent.

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 exactly three sentences, front-loaded with the core action, followed by cost and workflow in a logical order. Every sentence contributes essential information with no redundancy or filler.

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?

For a simple 3-parameter tool with no output schema, the description covers the key aspects: what it does, the cost, and the next step. It misses the return value structure, but the instruction to 'pass the result' implicitly acknowledges a result exists. Overall, it is nearly complete for the tool's complexity, though not exhaustive.

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?

Schema description coverage is only 33% (only 'amount' has a description). The tool description does not add meaning beyond the schema—it merely repeats the token enum values (ETH, USDG) already present in the schema. It fails to explain 'to' address format or the relationship between amount and cost, leaving the agent under-informed about parameter usage.

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 action: 'Constructs an unsigned ETH or USDG transfer transaction on Robinhood Chain.' It names the specific verb (constructs), resource (transfer transaction), and asset types (ETH/USDG), and distinguishes from sibling tools like broadcast (which signs and sends) and trade.

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 provides context on the intended workflow by saying 'Pass the result to the broadcast tool to actually sign and send it,' which implies when to use this tool vs. broadcast. However, it stops short of explicitly stating when not to use this tool or naming alternatives like trade or bridge, leaving some ambiguity for broader use cases.

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

Deploy Server