Skip to main content
Glama

SwitchWize MCP

Best Card For Spend

best_card_for_spend
Read-onlyIdempotent

Rank listed personal credit cards by estimated yearly rewards minus annual fee for a monthly spend profile (dining, travel, groceries, gas, other). Uses each card's own category earn rates and point value. Cards without a confirmed fee or earn rate for a category you spend in are left out. Excludes welcome bonuses, credits, interest and caps. Pay-in-full scenario, not personalized advice.

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": {
      "monthlySpend": "<monthlySpend>"
    },
    "name": "best_card_for_spend"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 5.
maxAnnualFeeNo
monthlySpendYesDollars per month. Omitted categories count as 0.
includeBusinessNoDefault false.

Output Schema

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

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, so the description is free to spend its words on behavior: the scoring formula, the omission rule for cards lacking a confirmed fee or category earn rate, and the explicit exclusions of welcome bonuses, credits, interest and caps. That tells the agent why results may be missing cards or look conservative — genuine value beyond the annotations. It stops short of covering data freshness or how ties/point valuations are resolved.

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?

Four tight sentences, front-loaded with the ranking logic, then omission rules, then exclusions, then the scope disclaimer. Every sentence carries information an agent would otherwise have to guess, and nothing is repeated from the schema or annotations.

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 return values need not be described, and the description covers methodology, omission behavior, and scenario limits well. The only gap is that the limit and maxAnnualFee filters — and the default exclusion of business cards — are never mentioned, though their schema descriptions largely carry that load.

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 75%, so the baseline is 3. The description restates the five spend categories and confirms category-level earn rates drive the ranking, which reinforces the nested monthlySpend object, but it adds no meaning for limit or maxAnnualFee and only obliquely implies the personal-vs-business default.

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 and resource ('Rank listed personal credit cards') plus the exact ranking criterion ('estimated yearly rewards minus annual fee') and the input shape ('monthly spend profile'). It also implicitly separates itself from the business-oriented sibling by scoping to personal cards, so an agent can tell what it does without opening the 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?

The scenario boundaries are stated clearly ('Pay-in-full scenario, not personalized advice') and the exclusions define when the ranking is valid, which is real usage framing. However, it never routes the agent away from alternatives such as compare_cards, cards_by_goal, or business_card_cost, so the when-to-use-vs-sibling decision is left to inference.

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.