SwitchWize MCP

Top Rates

get_top_rates

Read-onlyIdempotent

Return top SwitchWize rates for a supported category with freshness and attribution metadata.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`category`	Yes	Rate category, e.g. savings, cds, money-market, checking, mortgage.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

B3.2/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the description carries a lower burden. It adds that the results include freshness and attribution metadata, which is useful, but it does not mention pagination, default limit behavior, or what happens for unsupported categories.

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 one concise sentence, front-loaded with the action and resource, followed by the scope and metadata. There is no filler or redundant phrasing; every word contributes meaning.

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 two-parameter read tool with an output schema and comprehensive safety annotations, the description gives a solid picture. Minor additions such as noting category validation or limit defaults would improve completeness, but nothing essential is missing for a competent agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only the category parameter has a schema description; the limit parameter has none, and the tool description never mentions limit semantics. The phrase 'supported category' adds little beyond the schema's examples, so the undocumented limit parameter remains a real 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 states a clear action ('Return') and a specific resource ('top SwitchWize rates'), scoped to 'a supported category' and including freshness/attribution metadata. It is clearly a ranking/rates tool, but it does not explicitly differentiate itself from the sibling get_top_hysa_rates, so an agent may still wonder whether to use this or the more specific sibling.

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 guidance is given about when to use this tool versus alternatives such as get_top_hysa_rates or get_rate_freshness. The description only says what the tool returns, with no exclusions, prerequisites, or routing hints, despite a sibling list with several overlapping tools.

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.