Skip to main content
Glama

PointBagel

Card facts from the catalog

card_facts
Read-only

Published facts for ANY credit card in PointBagel's verified catalog: the card's earn rates by category, annual fee, the statement credits it carries by name with what each cap is based on and which are limited-time, the current public welcome offer and how it is available, and a link to apply. Works with no wallet connected. Use it for questions about a card in general, like what a card earns at restaurants, which credits come with it, or whether it has an offer right now. For the user's own cards - including a card they closed or converted - use card_detail instead; this tool knows nothing about who holds what. Facts are verified against issuer terms; 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": "card_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYesA card name or id, e.g. "Capital One Venture X" 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

A4.6/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds substantive context beyond them: no wallet/connection is required, the data covers any card including ones the user does not hold, facts are verified against issuer terms but are estimates rather than guarantees, and the tool has no visibility into cardholders. These are genuine behavioral traits an agent could not infer from the annotations.

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?

The scope statement is front-loaded and every sentence carries signal: facts enumerated, usage, exclusion, caveats. It runs long for a two-parameter tool, with a heavily elaborated middle list ('by name with what each cap is based on and which are limited-time'), but no sentence is truly disposable.

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?

An output schema exists, so return values need no explanation, and the description still covers scope, sibling exclusion, prerequisite state (no wallet needed), and a reliability caveat. For a read-only catalog lookup with two simple parameters, nothing an agent needs in order to call 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%, with both `card` (name or id, with examples) and `includeApplyLink` documented inline, so the baseline is 3. The description implies the apply-link dimension ('a link to apply') but never explicitly says the link is gated on includeApplyLink being true, adding little meaning 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?

The description opens with a specific verb-and-resource statement ('Published facts for ANY credit card in PointBagel's verified catalog') and enumerates exactly what those facts include: earn rates by category, annual fee, named statement credits with their caps and limited-time status, the current public welcome offer, and an apply link. It explicitly contrasts its scope with card_detail ('this tool knows nothing about who holds what'), so an agent can discriminate between the two without opening a schema.

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?

It gives a direct when-to-use rule ('questions about a card in general') with three concrete example intents, and a when-not-to rule pointing at the named sibling card_detail for the user's own, closed, or converted cards. It also notes the tool works with no wallet connected, removing a common prerequisite ambiguity.

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