Skip to main content
Glama

SwitchWize MCP

Cards By Goal

cards_by_goal
Read-onlyIdempotent

Return the cards on one SwitchWize goal page (cash-back, travel, no-annual-fee, zero-apr, building-credit, student, airline, hotel, store, no-foreign-transaction-fee, dining, groceries, gas) in the same order the page shows them, with how the list is chosen and how it is sorted.

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": {
      "goal": "<goal>"
    },
    "name": "cards_by_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes
limitNoDefault 10.

Output Schema

NameRequiredDescriptionDefault
asOfNoISO timestamp of the underlying data this response reflects.
goalNo
toolYes
cardsNo
countNo
errorNo
sourceNoWhere the data comes from (URL).
pageUrlNo
sortedByNo
toolMetaNoVersion and stability of the tool that produced this reply. See /developers#tool-versions.
goalLabelNo
attributionNo
generatedAtYesISO timestamp this response was computed at.
howWeChooseNo
verified_atNo
totalMatchedNo
schemaVersionYes
availableGoalsNo
methodologyUrlNo
freshnessStatusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: results preserve the page's display order and the response conveys how the list is chosen and sorted, which tells the agent not to re-sort or second-guess curation.

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

Conciseness3/5

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

It is a single front-loaded sentence, but the 13-item parenthetical duplicates the schema enum verbatim and inflates the sentence, while the trailing clause 'with how the list is chosen and how it is sorted' is grammatically loose about whether that is returned data or just a promise.

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 simple two-parameter lookup with read-only annotations and an output schema that documents the return shape, the description covers purpose, ordering, and curation logic adequately. It leaves minor gaps around limit behavior and whether the goal list is exhaustive, but nothing an agent needs to call it 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 description coverage is 50%, so the baseline is 3. The description restates the goal enum values, which the schema already enforces, and says nothing about the limit parameter beyond what the schema states ('Default 10.'), notably omitting that it caps how many cards are returned.

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 gives a concrete verb and resource ('Return the cards on one SwitchWize goal page') and enumerates the goal pages, so the agent knows exactly what data comes back. It does not name or differentiate against siblings like search_cards or compare_cards, which is the only thing keeping it from a 5.

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 only implied: an agent can infer 'use this when the user wants the cards for a named goal page.' There is no explicit when-to-use, no when-not-to-use, and no reference to alternatives such as search_cards for free-form queries, so routing decisions still require 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.