SwitchWize MCP

Official

by switchwize

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Top Rates

get_top_rates

Read-onlyIdempotent

Fetch ranked SwitchWize rates by category with freshness labels, using editor-approved snapshots for deposit accounts and returning no ranked rates for unapproved, stale, or unavailable releases.

Instructions

Return top SwitchWize rates with freshness and attribution. Savings, CDs, checking and money market answer only from their editor-approved snapshot. A category with no approved release yet returns no ranked rates and says so (approval_status: not_yet_approved) rather than serving unverified observations; approvedOnly makes that requirement explicit. Approved responses include product terms and field evidence; stale or unavailable releases return no ranked rates. detail=full (savings) adds the complete shared build: every listed account marked verified or tracked, best picks, movers, history and a headline summary.

Input Schema

TableJSON 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.
`category`	Yes	Rate category, e.g. savings, cds, money-market, checking, mortgage.
`approvedOnly`	No	Require an editor-approved deposit snapshot. Savings, CDs, checking and money market always answer from their own approved release; a category with no release yet returns no ranked rates (approval_status: not_yet_approved), as do stale or unavailable releases.

Output Schema

TableJSON 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
`dataStatus`	No
`attribution`	No
`emptyReason`	No
`generatedAt`	Yes
`schemaVersion`	Yes
`sourceDetails`	No
`methodologyUrl`	No
`freshnessStatus`	No
`attributionDetails`	No
`supportedCategories`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.0Oct 13, 2026

addedInput schema / properties / approvedOnly

Added value: +{
+  "description": "Require an editor-approved deposit snapshot. Savings, CDs, checking and money market always answer from their own approved release; a category with no release yet returns no ranked rates (approval_status: not_yet_approved), as do stale or unavailable releases.",
+  "type": "boolean"
+}

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"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "properties": {
+        "attribution": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "category",
+        "count",
+        "freshnessStatus",
+        "rates"
+      ]
+    },
+    {
+      "properties": {
+        "attribution": {
+          "additionalProperties": true,
+          "type": "object"
+        }
+      },
+      "required": [
+        "tool",
+        "error",
+        "attribution"
+      ]
+    }
+  ],
+  "properties": {
+    "asOf": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "attribution": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "additionalProperties": true,
+          "type": "object"
+        }
+      ]
+    },
+    "attributionDetails": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "category": {
+      "type": "string"
+    },
+    "count": {
+      "type": "number"
+    },
+    "dataStatus": {
+      "enum": [
+        "available",
+        "no_observations",
+        "no_eligible_rates",
+        "source_error",
+        "unavailable",
+        "stale",
+        "conflicted"
+      ],
+      "type": "string"
+    },
+    "emptyReason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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": {
+      "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"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "generatedAt"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 5, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds real context on top: the editor-approval gate, the not_yet_approved fallback, and that stale/unavailable releases yield no ranked rates. What it does not clarify is the default page size, ordering, or what 'field evidence' concretely contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the sentences are information-dense, but the approvedOnly and detail=full sentences duplicate the schema's parameter descriptions almost verbatim, which is wasted space. The jargon ('shared build', 'field evidence', 'movers') also goes unexplained.

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?

With an output schema present, the description needn't explain return values, and it does cover the key conditional behaviors (approval gating, staleness, detail levels). The gaps are the absence of sibling routing and the unspecified default/ordering for limit.

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 75% and the schema already documents approvedOnly and detail in detail. The description largely paraphrases those same parameter texts (approval_status, detail=full contents) rather than adding new syntax or constraints, so it lands at the baseline for well-covered schemas.

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 first sentence states a specific verb and resource ('Return top SwitchWize rates') plus the freshness/attribution framing, which is far more than the title restates. It does not, however, distinguish itself from the very close sibling get_top_hysa_rates or get_rate_freshness, so an agent still has to guess which 'top rates' tool applies.

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?

Usage is implied through category scoping ('savings, CDs, checking and money market answer only from their editor-approved snapshot'), but the description never says when to pick this over get_top_hysa_rates or the freshness/reality-score siblings. The reader must infer the boundary.

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

Deploy Server