Skip to main content
Glama

PointBagel

Which card to use

which_card
Read-only

Recommend which of the signed-in user's own credit cards to use for a given store or spending category, and show the earning behind the call: the effective earn rate, which reflects how much of that category cap the user has spent this period, or assumes none if PointBagel cannot see it, the estimated value per dollar, the runner-up cards in their wallet, any merchant-specific promotional rate with its terms, the booking channels that change the answer for travel, and any welcome-bonus spend in progress. Assumes a small default purchase when no amount is given. Values are estimates. Read-only; the user's own wallet only. For cards the user names but has not saved, use which_card_for_named_cards if it is available.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "which_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA store or spending category, e.g. "Costco", "dining", or "gas".
scopeNoLeave unset unless the member asks to limit to personal or business cards.
styleNoRedemption style for valuing points. Defaults to "balanced".
amountNoPurchase amount in US dollars. Defaults to a small purchase.
portalNoThe name of the travel portal the user says they are booking through, such as "Chase Travel", with bookingChannel set to portal.
businessNoA business name, as named in PointBagel, to rank only that business's cards. Implies scope "business", so it is part of the PRO plan.
bookingChannelNoHow the user says they are booking this purchase: direct with the supplier, through a portal (name it in portal), or other for any other way, such as an online travel agency. Put only the purchase in query. Leave this unset when the user has not said, has only said what they are not using, or is unsure; never assume it.
purchaseAbroadNoSet to true only when the user says the purchase is abroad or in a foreign currency; never assume it. For a spending category the answer then adds a ranking of the user's cards by what each earns minus its fee abroad.

Output Schema

NameRequiredDescriptionDefault
asOfYes
dataYes
statusYes
summaryYes
nextActionsNo
userWarningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/destructive/closed-world annotations it discloses real behavior: the effective earn rate depends on visible category-cap spend and falls back to 'no cap' when PointBagel cannot see it, values are estimates, a small default purchase is assumed when amount is absent, and travel answers shift by booking channel. It partly restates the annotations ('Read-only; the user's own wallet only'), which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and routing are front-loaded and the final sentences about assumptions and the sibling are tight. The middle is a single very long run-on list of outputs that is harder to scan than it needs to be, though nearly every clause carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter recommendation tool with annotations and an output schema, the description covers scope limits, fallbacks, estimation caveats, travel-specific channel behavior, and the alternative tool. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents every parameter including defaults and enums; baseline is 3. The description adds meaning only for amount (default small purchase) and partially for bookingChannel (channels 'change the answer for travel'), largely repeating what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource: 'Recommend which of the signed-in user's own credit cards to use for a given store or spending category.' It also enumerates what the recommendation contains (effective earn rate, value per dollar, runner-ups, promos, booking channels, welcome-bonus progress), and explicitly names the sibling case it does not handle ('cards the user names but has not saved' -> which_card_for_named_cards).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing to which_card_for_named_cards for unsaved cards, scopes usage to the user's own wallet, and notes the default-purchase assumption. Parameter-level guidance in the schema (leave scope unset, never assume bookingChannel or purchaseAbroad) reinforces when to apply each option, leaving little to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources