Skip to main content
Glama

transfer_usdt

Destructive

Sends USDT on Whitechain Sepolia within durable owner-defined spending limits. Reuse operation_id for retries; a submitted transfer is pending, not confirmed.

Instructions

Send USDT on Whitechain Sepolia through durable owner-defined spending limits. Reuse operation_id when retrying the same payment. A submitted state is pending, not confirmed.

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": {
      "recipient": "<recipient>",
      "amount": "<amount>"
    },
    "name": "transfer_usdt"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes
recipientYes
operation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Adds meaningful behavior beyond annotations: payments are bounded by durable owner-defined spending limits, and a submitted state is pending rather than confirmed, which tells the agent not to treat success as finality. The operation_id retry rule also explains how callers achieve idempotency despite idempotentHint=false — this is caller-supplied dedupe, not a contradiction of the annotation, but the description could have made that distinction explicit.

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?

Three short sentences, front-loaded with purpose and free of filler. Each sentence contributes a distinct fact: scope, retry rule, and finality semantics.

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

Completeness3/5

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

A destructive, open-world mutation with no output schema and no documented parameters needs more: what the response contains (operation id, tx hash, status), how pending resolves to confirmed, and what failure looks like when a spending limit is hit. The finality note is a good start but the definition stops short of complete.

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?

With 0% schema description coverage, the description carries the full burden. It explains operation_id semantics well, but leaves amount entirely unexplained (string — decimals or base units? what precision?) and says nothing about recipient beyond the hex pattern, e.g. whether it must be a Whitechain Sepolia address.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: send USDT on Whitechain Sepolia. The token and chain specificity inherently distinguishes it from transfer_wbt and pay, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Provides a concrete retry rule (reuse operation_id for the same payment), which is real guidance, but never says when to choose this over transfer_wbt, pay, or x402_fetch, nor any prerequisites such as having sufficient balance or an owner-defined limit in place.

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