Skip to main content
Glama

PointBagel

Prepare to save cards to your wallet

add_cards_preview
Read-only

Prepare to save credit cards to the user's PointBagel wallet, when the user asks to add or save cards they hold. Matches each name against PointBagel's catalog and says which cards would be saved, which are already in the wallet, and which need the PointBagel website instead: a second account of a card already in the wallet, cards the wallet holds only as closed, possible upgrades of a card they hold, and cards whose bonus categories they choose. Nothing is saved by this tool: it returns a save code that works once, for ten minutes. Show the user the cards, and save them with add_cards_confirm only after the user agrees. Include an opened month only when the user said it. Read-only.

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": {
      "cards": "<cards>"
    },
    "name": "add_cards_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardsYesThe cards the user asked to save, 1 to 10.

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?

Adds substantial context beyond the readOnly/destructive annotations: nothing is persisted, a single-use save code is returned, and it expires in ten minutes. The only gap is that it doesn't describe the shape of the preview result, though the output schema likely covers that.

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?

Front-loaded with the action, then the classification rules, then the confirmation workflow and the save-code caveat. Dense and purposeful, though the middle catalog-exception clause is a long run-on that could be split.

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?

Given an output schema exists and one fully documented parameter, this description supplies everything an agent needs: the trigger, the classification outcomes, the side-effect-free nature, the code lifetime, and the required confirm step.

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 coverage is 100%, so name and opened are already documented with examples. The description reinforces the 'include an opened month only when the user said it' constraint but adds no new syntax or semantics beyond the schema.

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?

States a specific verb and resource ('Prepare to save credit cards to the user's PointBagel wallet') and immediately clarifies it is a preview, not the save itself, which cleanly separates it from add_cards_confirm.

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?

Explicit trigger ('when the user asks to add or save cards they hold'), explicit next step ('save them with add_cards_confirm only after the user agrees'), and explicit exclusions routed elsewhere (second accounts of held cards, closed-only cards, upgrades, chosen bonus categories via the website).

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