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

TableJSON 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

TableJSON 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.

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

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds useful context beyond annotations by disclosing that results include a verified timestamp, source URL, and best-ever-for-route only when real history exists, giving agents insight into data provenance and conditional completeness.

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?

The description is a single, front-loaded sentence with no filler. It opens with the action and resource, then adds relevant data-quality detail without digression.

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?

This is a simple read-only tool with one optional parameter, full schema coverage, and an output schema. The description supplies the non-structured context an agent needs, such as verified timestamps, source URLs, and best-ever conditional logic, making it complete for correct invocation.

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%; the single optional program parameter is fully documented in the schema with example values (“chase-ultimate-rewards or Flying Blue”). The description does not add extra parameter-level meaning, so the baseline 3 is appropriate.

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 point-transfer bonuses across tracked bank-to-partner routes”), and the key data fields returned. This clearly distinguishes it from all 14 siblings, none of which target transfer bonuses.

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

Usage Guidelines4/5

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

The description immediately conveys when to use the tool: whenever current point-transfer bonuses for bank-to-partner routes are needed, with optional filtering by program. It does not explicitly name alternatives or exclusions, but the domain is distinct enough among siblings that usage intent is clear.

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.