Skip to main content
Glama

SwitchWize MCP

Compare Cards

compare_cards
Read-onlyIdempotent

Compare two to four listed credit cards side by side on confirmed terms, and name the leader for lowest annual fee, highest rewards rate, largest welcome bonus and longest 0% intro APR. A leader is chosen only among cards with a confirmed value for that term.

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": {
      "cards": "<cards>"
    },
    "name": "compare_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardsYesTwo to four card ids, slugs or names.

Output Schema

NameRequiredDescriptionDefault
asOfNoISO timestamp of the underlying data this response reflects.
noteNo
toolYes
cardsNo
countNo
errorNo
sourceNoWhere the data comes from (URL).
leadersNo
notFoundNo
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the computation rule: winners are named only among cards with a confirmed value for that term. That is genuine behavioral disclosure an agent could not infer from the schema or annotations, and it prevents misreading a missing leader as a tie. It stops short of saying what happens when no card has a confirmed value or how unconfirmed terms are surfaced.

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?

Two sentences, front-loaded with the action and scope, followed by the leader-selection caveat that qualifies the result. No restatement of the title and no filler.

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 input schema fully covers the lone parameter. What remains for the description — scope, evaluated terms, and the confirmed-value rule — is all present, which is enough for an agent to call this correctly.

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 single parameter already documents length bounds and accepted identifier forms ('card ids, slugs or names'). The description's only additional constraint is the adjective 'listed', hinting cards must exist in the catalog, which is marginal. Baseline 3 applies when the schema carries the parameter burden.

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 gives a specific verb ('Compare') and a precise resource ('two to four listed credit cards side by side'), then enumerates the exact terms evaluated (annual fee, rewards rate, welcome bonus, 0% intro APR). The word 'credit cards' alone separates it from siblings like compare_accounts and compare_switch_savings without needing to name them.

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: the 2-to-4 card bound and 'listed' qualifier tell an agent the shape of a valid call, but there is no explicit when-to-use or when-not-to-use framing. Nothing routes the agent to alternatives such as get_card_details for a single card or cards_by_goal for discovery.

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.