AbaPay
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| describe_capabilitiesA | List what AbaPay can pay (airtime, data, electricity, cable, etc.), any services currently paused, and example requests. Call this first if unsure what is supported. |
| check_balanceA | Check a linked wallet's stablecoin balances and remaining agent spending allowance. Works with no arguments once authorized via OAuth; otherwise pass the api_key. |
| list_plansA | List the REAL, currently purchasable plans for DATA, CABLE, or EDUCATION — exact codes and current prices. Always call before pay_bill for these three services. |
| list_international_optionsA | Browse the live international top-up catalogue (170+ countries) one level at a time: country → product type → operator → priced plan. |
| transaction_historyB | List recent real transactions for the linked wallet — service, provider, amount, status, tx hash. No PIN required. |
| pay_billA | Pay a real bill — Nigerian (airtime, data, electricity, cable, WAEC/JAMB) or international airtime/data — from the linked wallet, settled on-chain. Executes immediately; no delay parameter exists. |
| schedule_billB | Set up a recurring or future one-off bill payment. Charges nothing when this runs — money only moves later, when the schedule fires and the allowance still covers it. |
| list_schedulesC | List active recurring/one-off bill schedules for the linked wallet. No PIN required. |
| cancel_scheduleA | Cancel one or more active schedules. Pass id for exactly one, provider for all of that provider's, or neither to cancel everything. |
| pay_bill_batchB | Pay airtime or data to 2-20 recipients in one call, one PIN for the whole batch. All-or-nothing on capacity. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct operation: capabilities discovery, balance check, plan listing, international catalogue browsing, transaction history, schedule management (list/cancel/create), and payment (single or batch). The only close pair pay_bill/pay_bill_batch is clearly separated by recipient count (1 vs 2-20), and descriptions explicitly disambiguate.
Most tools follow verb_noun (check_balance, list_plans, cancel_schedule, pay_bill, schedule_bill, pay_bill_batch), and list_* groups are consistent. transaction_history breaks the pattern as a noun phrase rather than a verb-based action (e.g., get_transactions), but overall the naming is predictable.
10 tools provide a well-scoped surface for a bill-payment platform, covering capabilities, balances, plans, history, single/batch payments, and schedules without bloat. Each tool serves a clear purpose and the count is appropriate.
The server covers the main lifecycle: pay, schedule, list schedules, cancel, balance, history, and plan discovery. The only notable gap is no update operation for schedules—users must cancel and recreate—but this is a minor workaround. Overall the surface is nearly complete.