Skip to main content
Glama

PointBagel

Card details and credits

card_detail
Read-only

One credit card in detail, set against the rest of the signed-in user's wallet. The tool for the user's OWN card, including one they closed or converted: it reports whether they hold it now, held it before (with the card it became or came from), or never had it. For a held card: its earning structure, its statement credits by name with usage to date and each cap's basis, a personalized fee verdict once the card is tracked and holds one of the account's verdict slots, and a year-by-year scorecard of fees against benefits captured, each year marked scored or excluded and why. Catalog facts only when the user has no history with the card. Pass a card name or catalog id. Values are estimates.

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_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYes

Output Schema

NameRequiredDescriptionDefault
asOfYes
dataYes
statusYes
summaryYes
nextActionsNo
userWarningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint/destructiveHint it discloses the return semantics in detail: ownership resolution (now / before / never, with the predecessor or successor card), earning structure, statement credits with usage and cap basis, and scored-vs-excluded year markings. It also flags two behavioral constraints — the fee verdict only appears once tracked and occupying a verdict slot, and 'Values are estimates'. It does not cover failure behavior for an unknown or ambiguous card name.

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 core identity, then layered scope, then output shape, then the estimate caveat — a logical progression with little filler. The enumeration of returned fields is dense and partly overlaps the output schema, which keeps it from a 5.

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?

An output schema exists, so listing components such as credits and the scorecard is partly redundant, but the description adds what the schema cannot: ownership-era resolution, the verdict-slot precondition, exclusion reasons, and the estimate caveat. Missing only edge-case handling for unresolvable card inputs.

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

Parameters4/5

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

Schema coverage is 0% for the single 'card' parameter, so the description carries the burden, and it does the essential work by stating 'Pass a card name or catalog id' — a distinction the bare string schema cannot convey. It does not say how name collisions or fuzzy matches are resolved, so it is helpful but not fully compensatory.

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 concrete verb and resource — 'One credit card in detail, set against the rest of the signed-in user's wallet' — and immediately fixes scope as the user's OWN card, including closed or converted ones. The clause 'Catalog facts only when the user has no history with the card' implicitly separates it from the catalog-only sibling (card_facts) without needing that name.

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?

Gives clear selection context: use it for the user's own card, including a card they closed or converted, and it will report held/held-before/never-had. The fallback rule ('catalog facts only when the user has no history') further clarifies when this tool is the right one. It stops short of naming an alternative to use instead or an explicit when-not case.

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