Skip to main content
Glama

card_details

Read-only

Retrieve a credit card's base and accelerated reward rates, monthly cap usage for the current statement cycle, and reward balance by card ID or name.

Instructions

Everything about one card: base rate, accelerated earn rates, how much of each monthly cap is used in the current statement cycle, and its reward balance.

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

Input Schema

NameRequiredDescriptionDefault
cardYesCard id, or its name (a unique part is enough)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's main contribution is scope: it aggregates several data categories and scopes cap usage to 'the current statement cycle,' which is genuine behavioral context. Since an output schema exists, the field enumeration is largely redundant, and no latency, caching, or not-found behavior is disclosed.

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

Conciseness5/5

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

A single sentence with no filler, front-loading the scope ('Everything about one card') before the enumerated contents. Every clause earns its place.

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 one-parameter, read-only lookup with a full schema description and an output schema, the description covers scope and content adequately. The only meaningful omission is routing guidance relative to rewards_balance and list_cards, which an agent may plausibly confuse with this tool.

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% and the card parameter already documents that a card id or a unique name fragment is accepted. The description adds nothing about identifier format, ambiguity handling, or what happens if the fragment matches multiple cards. With the schema doing the work, the baseline of 3 applies.

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 (one card) and enumerates what is retrieved: base rate, accelerated earn rates, monthly-cap consumption, and reward balance. That is a concrete verb-plus-resource statement an agent can act on. It stops short of distinguishing itself from siblings such as rewards_balance or list_cards, which also touch card and reward data.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement, no when-not, and no named alternative. The phrase 'one card' implies a single-card lookup rather than a listing, but the agent is left to infer whether to call this or rewards_balance when reward balance is all that is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.