Skip to main content
Glama

SwitchWize MCP

Card Details

get_card_details
Read-onlyIdempotent

Return one listed credit card in full: fee, APR, intro APR, rewards and category rates, welcome bonus and requirement, perks and credits, foreign transaction fee, the issuer's own application-rule wording when published, and source freshness. Accepts a card id (issuer:slug), slug or name; an unknown card returns a structured error with suggestions.

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": "get_card_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYesCard id (issuer:slug), slug or name, e.g. chase:sapphire-preferred.

Output Schema

NameRequiredDescriptionDefault
asOfNoISO timestamp of the underlying data this response reflects.
cardNo
noteNo
toolYes
errorNo
sourceNoWhere the data comes from (URL).
toolMetaNoVersion and stability of the tool that produced this reply. See /developers#tool-versions.
attributionNo
generatedAtYesISO timestamp this response was computed at.
verified_atNo
schemaVersionYes
methodologyUrlNo
freshnessStatusNo
sourceFreshnessNo
applicationRulesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety bar is low. The description adds real value beyond that: it discloses the error contract ('an unknown card returns a structured error with suggestions') and that freshness and issuer rule wording are included only 'when published'.

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 action and scope, then a compact enumeration of returned fields, then the identifier/error behavior. The field list is long but each item carries information; no filler sentences or hedging.

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?

For a single-parameter read tool with an output schema and full annotation coverage, this is complete: it covers what is returned, accepted identifier formats, and the failure mode. Nothing an agent needs in order to invoke 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 coverage is 100% and the schema already documents the accepted forms (issuer:slug id, slug, or name) with an example. The description restates those accepted formats but adds no new syntax, normalization, or disambiguation rules, so it sits at the baseline.

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 specific verb and resource ('Return one listed credit card in full') and enumerates exactly what comes back: fee, APR, intro APR, rewards, welcome bonus, perks, foreign transaction fee. An agent can distinguish this detail-fetch from search_cards or compare_cards without opening any schema.

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 implied rather than stated: fetching a single card's full record, with the accepted identifier forms spelled out. There is no explicit when-to-use or when-not guidance pointing at siblings such as search_cards for discovery or compare_cards for side-by-side comparison, so the agent must infer the routing.

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.