Skip to main content
Glama
Sign In
t2000

t2000

by t2000-afi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

t2000_swap

Swap any token pair on Sui using Cetus Aggregator, which pools liquidity from 20+ DEXs. Accepts common names or full coin types; keep a small SUI balance for transaction gas.

Instructions

Swap tokens on Sui via Cetus Aggregator (20+ DEXs). Supports any token pair with liquidity. Use user-friendly names (SUI, USDC, USDsui, CETUS, DEEP, etc.) or full coin types. NOTE: Swap is NOT gasless — the wallet must hold some SUI for gas (typically < $0.01 per swap). Mirrors t2 swap <amount> <FROM> <TO>.

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": {
      "from": "<from>",
      "to": "<to>",
      "amount": "<amount>"
    },
    "name": "t2000_swap"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget token (e.g. "USDC", "CETUS", or full coin type)
fromYesSource token (e.g. "SUI", "USDC", or full coin type)
amountYesAmount of the source token to swap
slippageNoMax slippage (default 0.01 = 1%, max 5%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv9.12.0
  2. Removedv9.8.0
  3. Changed1 schema field changedv4.0.0
    • changedInput schema / properties / amount / description
      Previous value: -"Amount to swap"New value: +"Amount of the source token to swap"
  4. Addedv3.3.0
  5. Removedv2.12.0
  6. Addedv2.7.3
  7. Removedv2.7.1
  8. Addedv1.33.2
  9. Removedv1.32.0
  10. Addedv1.29.3
  11. Removedv1.28.0
  12. Addedv1.25.3
  13. Removedv1.25.0
  14. Addedv0.56.2

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It reveals that swaps are not gasless and gives typical gas cost, which is useful. However, it does not disclose slippage behavior, potential limits, or other side effects, which would be important for a swap 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 very concise with two sentences plus a note and CLI equivalent. All information is front-loaded and every sentence adds value.

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 no output schema and no annotations, the description is reasonably complete: it covers purpose, token naming, gas requirement, and references CLI. It omits return behavior but rules state output schema not required. Slippage details could be more explicit, but overall sufficient.

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?

Schema description coverage is 100%, but the description adds value by explaining that token parameters can be user-friendly names or full coin types, and mentions default slippage and max limit, providing extra context beyond the schema.

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 it swaps tokens on Sui via Cetus Aggregator, supports any token pair with liquidity, and specifies using user-friendly names or full coin types. It distinguishes from siblings like t2000_send and t2000_pay, which are different operations.

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 when to use it (for swapping tokens with any pair) and notes that it is not gasless and requires SUI for gas. However, it does not explicitly exclude alternatives or explain when to use this over sibling tools like t2000_agent_sell.

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