Skip to main content
Glama

PointBagel

Transfer bonuses

transfer_bonuses
Read-only

Transfer-bonus coverage across the programs PointBagel tracks: the bonuses live now and, optionally, the ones announced to start soon, with source and destination program, the standard and boosted ratios, each verified cap on the bonus in the units the issuer stated it (destination miles, source points, or an allowance shared across routes), per tier where tiered, any paid buy-up shown apart from the rates the member holds, the start and end dates, whether registration is required first, and whether the user holds the source currency. Bonus ratios are shown as a range when they vary by status tier or by card, never as a single number. Does NOT check live award availability. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "transfer_bonuses"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoOptional. "overview" returns a shorter answer with the main figures and every warning. "full" returns everything. Leave it out for the full answer.
programNoOptional: only show bonuses FROM this points program, e.g. "Chase Ultimate Rewards".
includeUpcomingNoInclude announced bonuses that have not started yet. Defaults to true.

Output Schema

NameRequiredDescriptionDefault
asOfYes
dataYes
statusYes
summaryYes
nextActionsNo
userWarningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 about the shape of the answer - caps quoted in issuer-stated units, paid buy-up shown apart from member rates, ratios expressed as a range, per-tier rows. That is meaningful behavioral disclosure beyond the annotation set, although the final 'Read-only' sentence merely restates the annotation.

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 is front-loaded in the opening clause and the sentence stays on topic, but it is one very long enumerated sentence that is hard to scan, and the trailing 'Read-only' duplicates the annotation.

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

Completeness3/5

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

An output schema exists, so most of the description's effort spent listing return fields is redundant, while genuinely useful gaps remain - nothing explains the overview vs full trade-off or how program matching works. It is adequate but allocates words to the wrong place given the structured fields available.

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 all three parameters (detail, program, includeUpcoming) are already documented in the schema, which sets the baseline at 3. The description only lightly gestures at includeUpcoming through 'optionally, the ones announced to start soon' and says nothing about detail modes or program filtering syntax.

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 the resource (transfer-bonus coverage across tracked programs) and enumerates the fields returned, so an agent can tell it is a read-only bonus lookup. It also carves out a boundary with 'Does NOT check live award availability,' though it never names a sibling tool it would be confused with.

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

Usage Guidelines3/5

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

Usage is only implied by the phrase 'across the programs PointBagel tracks' and by the note that it does not check award availability; there is no explicit 'use this when...' or routing to an alternative like best_redemption for award searches. An agent can infer intent but must guess at the boundary cases such as whether to call this when the user wants to know if a transfer is worth it yet.

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