Skip to main content
Glama
nasoma

Africa's Talking Airtime MCP

by nasoma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
api_keyYesYour Africa's Talking API key
countryYesYour country (e.g. kenya, uganda, dr congo, rwanda, south africa)
usernameYesYour Africa's Talking username
currency_codeYesCurrency code (e.g. KES, UGX, NGN)

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
check_balanceA

Checks the airtime balance of the Africa's Talking account.

This tool connects to the Africa's Talking API to fetch the user's
current application data, which includes the account balance.

Returns:
    str: A message displaying the account balance or an error if the
         balance cannot be retrieved.
load_airtimeA

Sends airtime to a specified phone number and logs the transaction.

This tool formats the phone number, sends the airtime using the
Africa's Talking API, and saves a record of the transaction in the
database.

Args:
    phone_number (str): The recipient's phone number.
    amount (float): The amount of airtime to send.
    currency_code (str): The currency for the transaction (e.g., "KES").

Returns:
    str: A message indicating the status of the airtime transaction.
get_last_topupsA

Retrieves the last N top-up transactions from the database.

Args:
    limit (int, optional): The number of recent transactions to fetch.
                           Defaults to 3.

Returns:
    str: A formatted string listing the last N transactions or a message
         if no transactions are found.
sum_last_n_topupsA

Calculates the sum of the last 'n' successful top-ups.

This tool retrieves the last 'n' transactions from the database and
calculates their total sum. It ensures that all transactions are in the
same currency before summing.

Args:
    n (int, optional): The number of recent top-ups to sum. Defaults to 3.

Returns:
    str: The total sum of the last 'n' top-ups or an error message if
         the currencies are mixed or no transactions are found.
count_topups_by_numberA

Counts the number of top-ups for a specific phone number.

Args:
    phone_number (str): The phone number to count transactions for.

Returns:
    str: The total count of top-ups for the given number or an error message.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: check_balance for account status, load_airtime for sending airtime, and three tools (count_topups_by_number, get_last_topups, sum_last_n_topups) for analyzing transaction history from different angles. The descriptions reinforce these distinct roles, making misselection unlikely.

Naming Consistency4/5

The naming follows a consistent snake_case pattern with clear verb_noun structures (e.g., check_balance, load_airtime). However, there is a minor deviation: 'count_topups_by_number' uses a prepositional phrase instead of a simple noun, slightly breaking the pattern compared to tools like 'get_last_topups' or 'sum_last_n_topups'.

Tool Count5/5

With 5 tools, the count is well-scoped for an airtime management server. It covers core operations (checking balance, sending airtime) and transaction analysis without being overwhelming, ensuring each tool earns its place in the workflow.

Completeness4/5

The toolset provides good coverage for airtime operations: checking balance, sending airtime, and analyzing transaction history. A minor gap exists in not having tools for managing transaction errors or refunds, but agents can likely work around this with the existing tools for core workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources