SwitchWize MCP

High-Yield Savings Rates

get_top_hysa_rates

Read-onlyIdempotent

Return top high-yield savings rates with freshness and attribution. Answers only from the editor-approved snapshot; before its first release it returns no ranked rates and says so (approval_status: not_yet_approved). approvedOnly makes the requirement explicit. detail=full adds every listed account marked verified or tracked, best picks, movers, history and a headline summary.

Input Schema

Name	Required	Description
`limit`	No
`detail`	No	summary (default) adds list_counts. full (savings) adds the complete shared build: accounts (verified and tracked, each marked), best_picks, movers, history and summary. rates stays verified-only either way.
`approvedOnly`	No	Require an editor-approved HYSA snapshot. The default tool already answers only from the approved release; before its first release it returns no ranked rates (approval_status: not_yet_approved).

Output Schema

Name	Required	Description	Default
`id`	No
`asOf`	No
`tool`	No
`count`	No
`error`	No
`rates`	No
`terms`	No
`source`	No
`category`	No
`rate_type`	No
`releaseId`	No
`dataStatus`	No
`attribution`	No
`emptyReason`	No
`generatedAt`	Yes
`releaseSize`	No
`releaseStatus`	No
`schemaVersion`	Yes
`sourceDetails`	No
`methodologyUrl`	No
`freshnessStatus`	No
`attributionDetails`	No
`supportedCategories`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026

addedOutput schema / properties / releaseId

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / releaseSize
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / releaseStatus

Added value: +{
+  "enum": [
+    "observed",
+    "unavailable"
+  ],
+  "type": "string"
+}

Changed7 schema fields changedOct 11, 2026

addedInput schema / properties / detail

Added value: +{
+  "description": "summary (default) adds list_counts. full (savings) adds the complete shared build: accounts (verified and tracked, each marked), best_picks, movers, history and summary. rates stays verified-only either way.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "attribution": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "category",
+      "count",
+      "freshnessStatus",
+      "rates"
+    ]
+  },
+  {
+    "properties": {
+      "attribution": {
+        "additionalProperties": true,
+        "type": "object"
+      }
+    },
+    "required": [
+      "tool",
+      "error",
+      "attribution"
+    ]
+  }
+]

addedOutput schema / properties / attribution / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]

removedOutput schema / properties / attribution / type
```
Removed value: -"string"
```

addedOutput schema / properties / error

Added value: +{
+  "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"
+}

addedOutput schema / properties / tool
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "schemaVersion",
-  "category",
-  "count",
-  "generatedAt",
-  "freshnessStatus",
-  "rates"
-]New value: +[
+  "schemaVersion",
+  "generatedAt"
+]

Changed2 schema fields changedOct 3, 2026

addedInput schema / properties / approvedOnly

Added value: +{
+  "description": "Require an editor-approved HYSA snapshot. The default tool already answers only from the approved release; before its first release it returns no ranked rates (approval_status: not_yet_approved).",
+  "type": "boolean"
+}

addedOutput schema / properties / dataStatus

Added value: +{
+  "enum": [
+    "available",
+    "no_observations",
+    "no_eligible_rates",
+    "source_error",
+    "unavailable",
+    "stale",
+    "conflicted"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedSep 17, 2026

addedOutput schema / properties

Added value: +{
+  "asOf": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "attribution": {
+    "type": "string"
+  },
+  "attributionDetails": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "category": {
+    "type": "string"
+  },
+  "count": {
+    "type": "number"
+  },
+  "emptyReason": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "freshnessStatus": {
+    "enum": [
+      "fresh",
+      "aging",
+      "stale",
+      "unavailable"
+    ],
+    "type": "string"
+  },
+  "generatedAt": {
+    "type": "string"
+  },
+  "id": {
+    "type": "string"
+  },
+  "methodologyUrl": {
+    "type": "string"
+  },
+  "rate_type": {
+    "enum": [
+      "APY",
+      "APR"
+    ],
+    "type": "string"
+  },
+  "rates": {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "schemaVersion": {
+    "type": "string"
+  },
+  "source": {
+    "type": "string"
+  },
+  "sourceDetails": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "supportedCategories": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "terms": {
+    "type": "string"
+  }
+}

addedOutput schema / required

Added value: +[
+  "schemaVersion",
+  "category",
+  "count",
+  "generatedAt",
+  "freshnessStatus",
+  "rates"
+]

Changed1 schema field changedSep 16, 2026

changedOutput schema / (root)

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

First observedSep 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare it read-only, idempotent, and non-destructive, but the description adds real behavioral context beyond them: the sourcing restriction to an editor-approved snapshot and the explicit degraded state (no ranked rates, approval_status: not_yet_approved) before first release. It also enumerates what detail=full surface area includes. Refresh/rate-limit behavior is still unstated.

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?

Three front-loaded sentences that lead with purpose and then qualify behavior; little waste. The approvedOnly sentence is somewhat redundant with the preceding snapshot sentence, costing a point.

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?

An output schema exists so return values need not be explained, yet the description still clarifies the meaningful state (approval_status: not_yet_approved) and the detail modes. Combined with the read-only annotations this is nearly complete; only the undocumented limit parameter remains a gap.

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 67% and both documented parameters (detail, approvedOnly) are essentially restated rather than clarified — the approvedOnly sentence largely duplicates the schema's own text. The limit parameter has no description in either place, so the description does not compensate for the coverage gap.

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 specific verb+resource ('Return top high-yield savings rates') plus the freshness/attribution wrapper, which is more precise than the bare title. It does not, however, differentiate itself from the close sibling get_top_rates, leaving the agent to infer the HYSA-specific scope.

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?

It states a meaningful operating condition — answers only from the editor-approved snapshot and returns no ranked rates with approval_status: not_yet_approved before first release. That is output-state guidance rather than when-to-use-this-vs-alternatives guidance; no sibling such as get_top_rates or compare_switch_savings is named as an alternative.

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.