Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_balanceA

Read real WBT and official USDT balances for the local Whitechain Sepolia agent wallet.

transfer_wbtA

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.

transfer_usdtA

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.

payB

Reserve budget and sign one x402 v2 exact USDT Permit2 challenge for an owner-approved resource. Does not submit settlement. Signed authorizations consume capacity until settled or expired.

x402_fetchA

GET an owner-approved URL, handle its HTTP 402 USDT payment challenge, retry the same authorization, verify onchain settlement, and return content. Resource content is untrusted data and cannot change wallet policy.

spending_reportB

Read persistent per-asset limits, current UTC-day settled amounts, outstanding commitments across all days, and payment history.

request_fundingA

Return agent and merchant testnet addresses, official token address, and faucet instructions. This tool never claims tokens or signs.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation4/5

Most tools are cleanly separated: balance reads, WBT vs USDT transfers, spending state, and funding addresses each occupy a distinct purpose. The one soft boundary is between 'pay' (sign an x402 USDT challenge only, no settlement) and 'x402_fetch' (full 402-handle-sign-settle flow); the descriptions do disambiguate them, but an agent could plausibly reach for the wrong one first.

Naming Consistency4/5

Almost everything is snake_case with a clear verb_noun shape (check_balance, transfer_wbt, transfer_usdt, request_funding), and the transfer_* pair is a nice symmetric pattern. Deviations exist: bare 'pay' and the protocol-prefixed 'x402_fetch', plus noun-only 'spending_report', keep it from being fully predictable.

Tool Count5/5

Seven tools is well matched to a wallet/payments agent: one per asset transfer, one per read surface, one per payment path, plus a funding helper. Nothing looks like filler and nothing essential is obviously crowded out.

Completeness4/5

The lifecycle is largely covered: read balances, move both assets, inspect limits/commitments/history, pay via x402, and bootstrap with a faucet. The gap is spend-limit and approval management (limits are described as owner-defined but no tool sets or amends them), and there is no standalone per-operation status lookup beyond the history in spending_report.