Skip to main content
Glama

transfer_wbt

Destructive

Send WBT on Whitechain Sepolia within owner-defined spending limits; reuse the same operation_id when retrying a payment, and treat submitted transfers as pending until confirmed.

Instructions

Send WBT 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_wbt"
  }
}

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?

Annotations already declare destructive, openWorld, and non-readOnly, so the safety profile is covered. The description adds real context beyond that: 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 settlement. It does not mention auth requirements or failure modes.

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, each carrying distinct information, with the core action front-loaded and the retry rule and state caveat following in priority order. No filler.

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?

For a destructive, open-world payment tool with no output schema and zero schema coverage, the description covers the pending-state caveat and retry key but omits amount formatting, confirmation behavior, and what a returned result contains. Adequate but with clear gaps.

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?

Schema description coverage is 0%, so the description must compensate. It explains operation_id's retry semantics well, but says nothing about amount units/decimals or the recipient's expected chain, leaving two of three parameters undocumented anywhere.

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 WBT on Whitechain Sepolia') plus the governing constraint (owner-defined spending limits). The token and chain naming implicitly separates it from transfer_usdt, but 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?

Gives one concrete usage rule — reuse operation_id when retrying the same payment — which is genuinely actionable. It offers no guidance on when to choose this over transfer_usdt, pay, or x402_fetch, so the when-to-use decision is only implied by the token name.

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