AwardWallet MCP
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusA | Shows which AwardWallet APIs this server can use and where each credential comes from, whether demo or read-only mode is on, and how many people and accounts the AwardWallet Business account can see. Useful to explain missing data or configuration errors. |
| list_peopleA | Lists the people whose loyalty accounts your AwardWallet Business account can see: connected AwardWallet users (with the account and trip access each one granted) and members you added in the business interface, with how many accounts each has. Returns the userId and memberId values other tools accept. |
| list_loyalty_accountsA | Lists loyalty accounts (airline miles, hotel points, credit-card rewards, rentals, shopping, ...) with balance, elite status, last change, update status and everything that expires on them (points, certificates and other sub-accounts such as free nights or companion passes, elite status), one compact row per account, plus a summary of upcoming expirations and accounts with update problems. Filter by person, program, type, balance or an expiration date. For one account's full properties and transaction history use get_loyalty_account. |
| get_loyalty_accountA | Returns one loyalty account in full: balance, every tracked property (elite status, account number, points to next level, ...), sub-accounts such as individual cards, links to update it on AwardWallet, and its transaction history, paginated. |
| get_travel_timelineA | Lists trips from AwardWallet's travel timeline (flights, hotels, car rentals, trains, buses, cruises, ferries, transfers, parking and events) with dates, confirmation numbers, travelers and locations, sorted by start date, for a date window (default: today through 12 months ahead). Only connected users who share trips are covered, and AwardWallet requires a paid Business subscription with timeline export approval. |
| search_loyalty_programsA | Searches the loyalty programs AwardWallet supports by name or code (e.g. 'hyatt', 'avios', 'membership rewards'), optionally by type. Returns program codes for get_loyalty_program. |
| get_loyalty_programA | Returns what AwardWallet knows about one loyalty program: its login fields, the properties it tracks (elite status, expiration, ...), how many elite levels it has, and what AwardWallet can do with it (transaction history, itineraries, reservation lookup, expiration tracking). |
| search_api_operationsA | Searches the raw AwardWallet API operations this server can call, across the Account Access, Web Parsing (Loyalty), Email Parsing, Credit Card Bonus, Flight Award Search and Hotel Award Search APIs (https://awardwallet.com/api/main). Returns each match's id, whether it reads or writes, its documentation link and the JSON Schema of its input. An empty query lists every available operation briefly. |
| call_api_read_operationA | Runs a read-only AwardWallet API operation (access=read in search_api_operations) and returns AwardWallet's JSON response. Refuses write operations. API reference: https://awardwallet.com/api/main. |
| call_api_write_operationA | Runs an AwardWallet API operation that creates, changes or deletes data, signs in to a loyalty or mailbox account, or starts billable work (access=write in search_api_operations). When it needs a password or token, it returns a one-time link to a local page where the user types it, so the secret never passes through the conversation. API reference: https://awardwallet.com/api/main. |
| get_secure_input_resultA | Returns the status of a request waiting on the secure input page (waiting, completed, failed, cancelled or expired) and, once completed, AwardWallet's response. |
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 11 tools
Specific read tools for loyalty accounts, programs, and timeline are clearly distinct, but the generic search_api_operations and call_api_read/write_operation create ambiguity about when to use a specific tool versus a raw API call, and get_status partially overlaps with search_api_operations' inventory.
All tools use snake_case with consistent verb-first naming (get_, list_, search_, call_) and no mixed conventions; the pattern is predictable and readable.
11 tools is well-scoped for an API wrapper, covering status, core entities, search, generic API calls, and secure input without excessive fragmentation.
Read coverage is thorough for people, loyalty accounts, programs, and trips, and generic read/write operations fill gaps for mutations, but dedicated tools for common write operations (e.g., creating/updating accounts) are absent, forcing agents to use lower-level API calls.