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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
wallet_statusB

Wallet address, XNO balance, and pending incoming amounts

x402_quoteA

Fetch an x402 endpoint's payment quote WITHOUT paying. Returns price in XNO, destination, and the full offer menu.

x402_compareA

Price the same API call on EVERY rail the server offers (Base/Solana USDC, Lightning, XNO...) from live data — use this to verify which rail is cheapest instead of trusting documentation.

x402_payA

Request a URL and automatically pay its Nano x402 quote (feeless, sub-second). Refuses quotes above max_xno. Returns the paid response body and the settlement receipt.

faucet_claimA

Claim free starter XNO from a Feeless402 faucet (solves the faucet's proof-of-work challenge automatically; may take ~1 min of CPU). Use when the wallet is empty.

topup_quoteA

Quote a small swap from another asset (e.g. USDC-BASE, USDT-SOL) into XNO for topping up the wallet. Execution requires NANSWAP_API_KEY; this tool only quotes.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct action: wallet status, quote retrieval, cross-rail comparison, payment execution, faucet claim, and swap quote. The x402_* prefix groups the payment flow while the others are clearly separate operations.

Naming Consistency4/5

Names are snake_case and mostly use a resource_action pattern (wallet_status, x402_pay, faucet_claim), but the x402_ prefix creates a subgroup and topup_quote is action-first. Minor inconsistency, but all are readable and predictable.

Tool Count5/5

Six tools is well-scoped for a nano-payment server, covering the essential operations without redundancy or bloat. Each tool earns its place.

Completeness4/5

The core lifecycle is covered: get funds (faucet), check balance, quote, compare rails, pay, and top-up quote. Missing direct transfer or history tools, but these are out of scope for the x402-focused design.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive