Skip to main content
Glama
Sign In
t2000

t2000

by t2000-afi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

t2000_send

Transfer USDC, USDsui, or SUI to any Sui address or SuiNS name. Requires explicit asset selection; stablecoin sends are gasless; dryRun previews without signing.

Instructions

Send USDC, USDsui, or SUI to a 0x Sui address or a SuiNS name (e.g. alex.sui). Amount is in token units (1 USDC = $1). Asset is REQUIRED — there is no implicit USDC default. USDC + USDsui sends are gasless (Sui foundation sponsored); SUI sends require gas. Set dryRun: true to preview without signing. Mirrors t2 send <amount> <ASSET> <recipient>.

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>",
      "asset": "<asset>"
    },
    "name": "t2000_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient: 0x Sui address or SuiNS name like 'alex.sui'.
assetYesREQUIRED — one of USDC, USDsui, SUI. No default.
amountYesAmount in token units to send
dryRunNoPreview without signing (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv9.12.0
  2. Removedv9.10.0
  3. Changed1 schema field changedv9.4.0
    • changedInput schema / properties / to / description
      Previous value: -"Recipient: 0x Sui address, SuiNS name like 'alex.sui', or saved contact name."New value: +"Recipient: 0x Sui address or SuiNS name like 'alex.sui'."
  4. Changed6 schema fields changedv4.0.0
    • changedInput schema / properties / amount / description
      Previous value: -"Amount in dollars to send"New value: +"Amount in token units to send"
    • addedInput schema / properties / amount / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / asset / description
      Previous value: -"Asset to send (default: USDC)"New value: +"REQUIRED — one of USDC, USDsui, SUI. No default."
    • addedInput schema / properties / asset / enum
      Added value: +[
+  "USDC",
+  "USDsui",
+  "SUI"
+]
    • changedInput schema / properties / to / description
      Previous value: -"Recipient: 0x Sui address, SuiNS name like 'alex.sui', or saved contact name. SuiNS preferred; contact aliases are deprecated."New value: +"Recipient: 0x Sui address, SuiNS name like 'alex.sui', or saved contact name."
    • changedInput schema / required
      Previous value: -[
-  "to",
-  "amount"
-]New value: +[
+  "to",
+  "amount",
+  "asset"
+]
  5. Addedv3.3.0
  6. Removedv2.12.0
  7. Addedv2.7.3
  8. Removedv2.7.1
  9. Addedv1.33.2
  10. Removedv1.32.0
  11. Addedv1.29.3
  12. Removedv1.28.0
  13. Addedv1.25.3
  14. Removedv1.25.0
  15. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description discloses key behaviors: gasless for USDC/USDsui, gas required for SUI, and dry-run capability. It also clarifies asset requirements and unit interpretation. Missing details on return values or error handling, but overall transparent for a send tool.

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 concise, with 3 sentences plus a command reference mirror. It is front-loaded with the core action and then provides important nuances. Every sentence adds meaningful information, with no redundancy.

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 4 parameters, no output schema, and no annotations, the description covers all parameter semantics, usage context, and key behaviors. It is almost complete, though a note on the return format (e.g., transaction hash) would enhance completeness.

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 schema covers all 4 parameters with descriptions. The description adds value beyond schema by explaining that amount is in token units (1 USDC = $1), that asset is required with no default, and the effect of dryRun. This enriches the semantic understanding.

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 (Send), resources (USDC, USDsui, SUI), and recipients (0x Sui address or SuiNS name). It distinguishes the tool's function from siblings by specifying supported assets and recipient types, making its purpose unambiguous.

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 clear context for when to use the tool: sending specific tokens to Sui addresses or names. It includes practical notes on gas requirements and dry-run functionality. However, it does not explicitly mention when not to use it or suggest alternative sibling tools like t2000_pay.

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

Deploy Server

Other Tools