SwitchWize MCP

Card Offers

get_card_offers

Read-onlyIdempotent

Return current credit-card welcome-bonus offers (non-targeted, confidence-gated), each with a verified timestamp, source URL, and the card's own 12-month best.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`card`	No	Optional card id (issuer:slug), slug, or name to filter to one card, e.g. chase:sapphire-preferred or Sapphire Preferred.
`limit`	No

Output Schema

TableJSON Schema

Name	Required	Description
`asOf`	No	ISO timestamp of the underlying data this response reflects.
`tool`	Yes
`count`	No
`error`	No
`offers`	No
`datasetUrl`	No
`attribution`	No
`generatedAt`	Yes	ISO timestamp this response was computed at.
`verified_at`	No
`totalTracked`	No
`schemaVersion`	Yes
`methodologyUrl`	No
`freshnessStatus`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026
- addedOutput schema / properties / error / properties / retryable
```
Added value: +{
+  "type": "boolean"
+}
```

Changed2 schema fields changedSep 17, 2026

addedOutput schema / properties

Added value: +{
+  "asOf": {
+    "description": "ISO timestamp of the underlying data this response reflects.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "attribution": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "count": {
+    "type": "number"
+  },
+  "datasetUrl": {
+    "type": "string"
+  },
+  "error": {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "suggestions": {
+        "items": {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "code",
+      "message"
+    ],
+    "type": "object"
+  },
+  "freshnessStatus": {
+    "enum": [
+      "fresh",
+      "aging",
+      "stale",
+      "unavailable"
+    ],
+    "type": "string"
+  },
+  "generatedAt": {
+    "description": "ISO timestamp this response was computed at.",
+    "type": "string"
+  },
+  "methodologyUrl": {
+    "type": "string"
+  },
+  "offers": {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "schemaVersion": {
+    "type": "string"
+  },
+  "tool": {
+    "type": "string"
+  },
+  "totalTracked": {
+    "type": "number"
+  },
+  "verified_at": {
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedOutput schema / required

Added value: +[
+  "schemaVersion",
+  "tool",
+  "generatedAt"
+]

Changed1 schema field changedSep 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

AddedSep 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering safety. The description adds valuable context beyond annotations by specifying the output content (verified timestamp, source URL, card's own 12-month best) and the confidence-gating filter. This enriches the agent's understanding of what to expect without contradicting annotations.

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 that is front-loaded with the core purpose and packs essential qualifiers without wasted words. Every phrase adds meaning, and it is appropriately brief for the tool's simplicity.

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?

Given the output schema exists, return format is covered. Annotations handle safety. The description adds the key qualifiers (non-targeted, confidence-gated) and output fields (timestamp, URL, 12-month best). It lacks details on how the limit parameter works, but that is minor given the schema. Overall, an agent has enough to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% (only 'card' has a description; 'limit' only has min/max). The tool description does not compensate for the undocumented 'limit' parameter or add any semantics beyond what the schema provides. Since the description mentions nothing about parameters, it fails to help the agent understand how limit affects results.

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 states a specific verb (Return), a precise resource (current credit-card welcome-bonus offers), and important qualifiers (non-targeted, confidence-gated) that distinguish it from sibling tools like get_card_changes or get_transfer_bonuses. The mention of 'current' and '12-month best' further narrows scope, making the tool's purpose unambiguous.

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 description provides clear context (current, non-targeted welcome-bonus offers) but does not explicitly mention alternatives or when not to use this tool. It implies usage for welcome-bonus offers but gives no exclusions or routing to siblings like get_card_changes or get_transfer_bonuses, so guidance is only implicit.

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

All SwitchWize MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.