rightcard-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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| best_cardA | Which of the given cards earns the most at a store (merchant) or for a spend category, today. Returns the card, the honest rate, why, and caveats (merchant-code traps, activation, ties). Base rates + rotating bonuses + built-in card benefits only; a user's personal bank offers live on their phone and are not consulted here. |
| lookup_merchantB | The store's reward category as RightCard's directory files it, its merchant type, and the merchant-code caveat when a category bonus usually will not post there (superstores like Walmart/Target, warehouse clubs like Costco/Sam's). Same ranking the app uses. |
| search_cardsA | Search RightCard's catalog by card or issuer name to get the ids to pass into best_card. Verified cards first; unverified cards are flagged, never hidden. |
| cardB | Everything RightCard knows about one card: rates by category, base rate, currency, annual fee, verification status, live rotating windows, and the choose-your-category spec if it has one. |
| rotating_calendarA | Live and upcoming rotating-category windows (Freedom Flex, Discover it, Citi Dividend…) and permanent merchant benefits, from the same verified data as the app. Optionally filter by card id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| which-card | Ask RightCard for the best card at a store, given the cards you hold. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| catalog | |
| valuation |
TDQS
Scored across 5 tools
Each tool has a clear, distinct purpose: best_card compares cards, lookup_merchant provides merchant category info, search_cards finds card IDs, card gives detailed card data, and rotating_calendar lists rotating offers. There is no overlap or ambiguity between them.
All tool names use snake_case and are readable. Most follow verb_noun pattern (lookup_merchant, search_cards) but 'card' and 'rotating_calendar' differ slightly; still, the style is consistent and predictable.
With 5 tools, the server is well-scoped for its purpose of card rewards recommendations. Each tool is necessary and not redundant, fitting comfortably in the ideal 3-15 range.
The domain of finding the best card for a merchant or category is fully covered: search for cards, retrieve card details, check merchant categories, compare cards, and consult rotating offers. There are no obvious missing operations for this specific use case.