SwitchWize MCP

Official

by switchwize

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Compare Savings Rates

compare_switch_savings

Read-onlyIdempotent

Compares your current APY with SwitchWize's top savings APY for a chosen balance, revealing the potential savings gap.

Instructions

Compare a user's current APY with SwitchWize's current top savings APY for a balance.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`balance`	No
`currentApy`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`asOf`	No	ISO timestamp of the underlying data this response reflects.
`tool`	Yes
`error`	No
`balance`	No
`annualGap`	No
`currentApy`	No
`attribution`	No
`generatedAt`	Yes	ISO timestamp this response was computed at.
`verified_at`	No
`comparisonApy`	No
`schemaVersion`	Yes
`methodologyUrl`	No
`currentInterest`	No
`freshnessStatus`	No
`breakEvenFraming`	No
`comparisonInterest`	No
`recommendationStatus`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Oct 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "annualGap": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "asOf": {
+      "description": "ISO timestamp of the underlying data this response reflects.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "attribution": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "balance": {
+      "type": "number"
+    },
+    "breakEvenFraming": {
+      "type": "string"
+    },
+    "comparisonApy": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "comparisonInterest": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "currentApy": {
+      "type": "number"
+    },
+    "currentInterest": {
+      "type": "number"
+    },
+    "error": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retryable": {
+          "type": "boolean"
+        },
+        "suggestions": {
+          "items": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "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"
+    },
+    "recommendationStatus": {
+      "enum": [
+        "comparison_available",
+        "data_unavailable"
+      ],
+      "type": "string"
+    },
+    "schemaVersion": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "verified_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "tool",
+    "generatedAt"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 5, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that the comparison is against a live 'current' top APY for a given balance, but says nothing about rate freshness, data source, or response shape.

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 tight sentence with the comparison target and scoping input front-loaded. No waste, though it is perhaps over-compressed for a tool with two non-obvious parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 explained, and the read-only annotations cover safety. Still missing is any note on which rate source backs the 'top APY' and whether the optional balance changes the result, which the agent needs to invoke confidently in this sibling-heavy cluster.

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 0%, so the description must carry the burden: it names both parameters implicitly ('current APY', 'balance') and gives each meaning. However, it adds no units or format detail (e.g. APY as a percent number vs decimal, balance currency), which matters given the schema's max of 25 on currentApy.

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 (compare) and both resources (the user's current APY vs SwitchWize's top savings APY) scoped by balance. An agent can tell what it does, though it does not explicitly distinguish itself from rate-list siblings like get_top_hysa_rates or get_bank_gap.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives in a crowded sibling set (get_top_hysa_rates, get_bank_gap, best_move_this_week). Usage must be inferred entirely from the single purpose sentence.

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

Deploy Server