SwitchWize MCP

Transfer Bonuses

get_transfer_bonuses

Read-onlyIdempotent

Return current point-transfer bonuses across tracked bank-to-partner routes, each with a verified timestamp, source URL, and best-ever-for-route when real history exists.

Input Schema

Name	Required	Description	Default
`program`	No	Optional program id or name to filter routes by source or destination, e.g. chase-ultimate-rewards or Flying Blue.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 11, 2026
- removedOutput schema / properties / error / properties / suggestions / items / additionalProperties
```
Removed value: -true
```
- addedOutput schema / properties / error / properties / suggestions / items / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]
```
- removedOutput schema / properties / error / properties / suggestions / items / type
```
Removed value: -"object"
```
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"
+  },
+  "routes": {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "schemaVersion": {
+    "type": "string"
+  },
+  "tool": {
+    "type": "string"
+  },
+  "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

B3.2/5.0

Behavior3/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 profile is covered. The description adds one genuinely useful behavioral trait: 'best-ever-for-route when real history exists,' disclosing that a field is conditionally populated. Everything else it mentions (timestamp, source URL) restates return values already covered by the output schema.

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?

A single front-loaded sentence with no filler; the core action leads and the output details follow. Slightly dense and could be split, but nothing is wasted.

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 read-only tool with one optional parameter, a full schema, and an output schema, the description covers purpose and return provenance adequately. The only real gap is routing guidance against the many sibling tools in this rate/deal family.

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 100%, and the single optional 'program' parameter is fully documented as filtering by source or destination with examples. The description adds nothing about filtering semantics, so baseline 3 applies.

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?

States a specific verb and resource ('Return current point-transfer bonuses') and scopes it to 'tracked bank-to-partner routes,' which clearly separates it from rate, card-offer, and valuation siblings. It does not name a sibling, but the domain is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of alternatives (e.g. get_card_offers, best_move_this_week), and no prerequisites. The usage context is only implied by the resource name.

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.