Skip to main content
Glama

PointBagel

Welcome offer and bonus progress

welcome_offer
Read-only

Welcome-offer coverage for one credit card: the current published offer (bonus, minimum spend, time window, and when PointBagel verified it), how the offer is available (public, through the application flow, targeted or variable, by referral, no public offer, or not recently verified), a verified finding when a card has no public offer, and, for a card the user owns, their estimated progress toward the bonus from imported transactions. Use it to judge how strong an offer is and whether to apply now or wait. Estimates, not guarantees. 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": {
      "card": "<card>"
    },
    "name": "welcome_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYesA card name or id, e.g. "Marriott Bonvoy Brilliant" or "chase_sapphire_preferred".
includeApplyLinkNoSet to true when the user is asking about applying for this card.

Output Schema

NameRequiredDescriptionDefault
asOfYes
dataYes
statusYes
summaryYes
nextActionsNo
userWarningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real context on top: provenance ('when PointBagel verified it'), data source for progress ('imported transactions'), and an accuracy caveat ('Estimates, not guarantees'). It does not discuss staleness handling or what happens when verification is missing, but the added value is well above the annotation baseline.

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

Conciseness3/5

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

The lead clause is front-loaded correctly, but the whole definition is one long run-on sentence whose parenthetical list of six availability modes ('public, through the application flow, targeted or variable, by referral, no public offer, or not recently verified') is dense and could be structured as a short list. The content earns its place, but the presentation impedes scanning.

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

Completeness4/5

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

For a read-only lookup with an output schema, this covers the essentials: what is returned, whose data it uses (owned cards, imported transactions), accuracy caveats, and the decision it supports. It only misses how an unverified or unavailable state should be interpreted by the agent.

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 both 'card' and 'includeApplyLink' are already documented in the schema, and the description adds nothing about the apply-link flag. Baseline 3 is appropriate — the enumeration of offer states gestures at the domain, but it adds no parameter-level meaning.

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

Purpose4/5

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

The description names a specific resource and scope: welcome-offer coverage for a single credit card, enumerating exactly what comes back (current published offer, availability mode, verified no-offer finding, and bonus progress for owned cards). It is clear without opening a schema, though it never explicitly contrasts itself with close siblings such as card_detail or application_eligibility, leaving that separation to be inferred.

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

Usage Guidelines4/5

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

It gives a concrete decision context: 'Use it to judge how strong an offer is and whether to apply now or wait,' which tells the agent when this tool is the right one. It stops short of naming an alternative tool or stating when not to use it, so there is no explicit routing rule.

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