Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SMARTCARD_DBNoPath to the SQLite database file used for storage. Defaults to ~/.smartcard/smartcard.db.~/.smartcard/smartcard.db

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

SmartCard (by Shubham Kumar Sahoo) tracks the user's credit cards and tells them which card to use for each purchase.

  • Amounts are in Indian rupees (INR).

  • Start with list_cards. If the wallet is empty, help the user add a card with add_card and then add_earn_rate for each accelerated reward category.

  • Earning model: every block_inr rupees earns base_rate units. Earn rates replace the base rate for matching categories or merchants and may have a monthly cap; spend past the cap earns the base rate.

  • Never invent reward rates. Use search_card_terms, show the user what you found, and save only what they confirm.

  • Ask the user before removing cards or purchases.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_cardsA

List every card in the wallet with its base earning rate.

card_detailsB

Everything about one card: base rate, accelerated earn rates, how much of each monthly cap is used in the current statement cycle, and its reward balance.

add_cardA

Add a credit card to the wallet, then call add_earn_rate for each category or merchant where it earns more than its base rate.

Wrong terms silently skew every later recommendation, so saving needs the user's
agreement: call once without `confirmed` to get a preview, show it to the user
(including anything found with search_card_terms and their statement day), and
call again with confirmed=true only after they agree.
update_cardB

Change details of an existing card. Only the fields you pass are changed.

remove_cardA

Delete a card and all its earn rates, purchases and point adjustments. Call once without confirm to see what would be deleted, then ask the user.

add_earn_rateA

Add an accelerated reward rate to a card for a category, a merchant, or both. When several rates match a purchase, the most specific one wins (merchant beats category). Only add rates the user has confirmed.

remove_earn_rateA

Delete one earn rate (ids are shown by card_details).

recommend_cardA

Rank every card in the wallet by the rupee value it would give back on this purchase, taking monthly caps already used into account.

log_purchaseB

Record a purchase made on a card and calculate the rewards it earned. Also says whether another card in the wallet would have earned more.

list_purchasesB

Show purchases, newest first, optionally filtered.

delete_purchaseA

Delete a purchase logged by mistake. Ask the user first.

rewards_balanceB

Reward balance per card: earned from purchases, plus or minus manual adjustments, and what the balance is worth in rupees.

adjust_rewardsA

Record points or cashback that did not come from a purchase.

spending_reportA

Spending and rewards by category and by card. With no dates, covers the current calendar month.

search_card_termsA

Search the web for a card's published reward terms. Results are raw snippets: summarise them for the user and confirm before saving anything.

Prompts

Interactive templates invoked by user choice

NameDescription
set_up_cardWalk the user through adding a card with correct reward rates.

Resources

Contextual data attached and managed by the client

NameDescription
categoriesSpending categories SmartCard understands.

TDQS

A3.7/5.0

Scored across 15 tools

Disambiguation4/5

Each tool targets a distinct resource+action (cards, earn rates, purchases, rewards, reports), and the confirmation-flow tools (add_card, remove_card) are explicitly documented. Minor overlap exists between card_details (which includes reward balance) and rewards_balance, but the descriptions make the intended split clear enough.

Naming Consistency4/5

Mostly a clean verb_noun snake_case pattern (list_cards, add_card, remove_card, add_earn_rate, log_purchase, delete_purchase, adjust_rewards). A few outliers are noun-only (card_details, rewards_balance, spending_report), which breaks the pattern slightly but remains readable and predictable.

Tool Count5/5

15 tools is within the well-scoped range and each one maps to a concrete operation in a wallet/rewards domain. Nothing appears redundant or padded.

Completeness4/5

Cards, earn rates, purchases, rewards, and reporting all have lifecycle coverage, including a search tool for reward terms and preview/confirm flows for destructive operations. Gaps are minor: there is no update_purchase or update_earn_rate (users must delete and re-add), which agents can work around.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues