SwitchWize MCP

Official

by switchwize

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Data Freshness

get_rate_freshness

Read-onlyIdempotent

Check public rate source freshness and affected routes before relying on savings, CD, money-market, checking, macro, or index data; unavailable sources are flagged.

Instructions

Return public data source freshness status and affected routes. savings is an alias for hysa; money-market is an alias for mma. Also supports cds, checking, macro, bank-gap-index, and indices. Omit category for all supported sources. Unknown categories return an error; a source with no observations is explicitly unavailable. Source collection freshness does not establish that a ranked deposit release is approved or current.

Input Schema

Name	Required	Description	Default
`category`	No	Optional freshness category. savings maps to hysa; money-market maps to mma. Also supports cds, checking, macro, bank-gap-index, and indices. Omit for all supported sources. Unknown values return an error; a known source without observations is unavailable.

Output Schema

Name	Required	Description
`tool`	Yes
`error`	No
`sources`	No
`attribution`	No
`generatedAt`	Yes	ISO timestamp this response was computed at.
`schemaVersion`	Yes
`affectedRoutes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.1Oct 28, 2026

addedInput schema / properties / category / description

Added value: +"Optional freshness category. savings maps to hysa; money-market maps to mma. Also supports cds, checking, macro, bank-gap-index, and indices. Omit for all supported sources. Unknown values return an error; a known source without observations is unavailable."

addedInput schema / properties / category / enum

Added value: +[
+  "savings",
+  "hysa",
+  "cds",
+  "money-market",
+  "mma",
+  "checking",
+  "macro",
+  "bank-gap-index",
+  "indices"
+]

Changed1 schema field changedv0.3.0Oct 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "affectedRoutes": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "attribution": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "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"
+    },
+    "generatedAt": {
+      "description": "ISO timestamp this response was computed at.",
+      "type": "string"
+    },
+    "schemaVersion": {
+      "type": "string"
+    },
+    "sources": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "tool",
+    "generatedAt"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, open-world. The description adds genuine behavioral context beyond them: unknown categories raise an error, sources with no observations are reported as unavailable rather than empty, and freshness is a collection signal not an approval signal. That last caveat is a meaningful semantic distinction the annotations cannot express.

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?

The core purpose and the alias rules are front-loaded, and each sentence carries information. It is slightly padded by re-enumerating categories and aliases that the schema already lists, which is duplication rather than new value.

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 zero-required-parameter read tool with a full output schema, the definition covers purpose, aliasing, error behavior, empty-source semantics, and the approval caveat—enough to call it correctly. 'Affected routes' is mentioned without elaboration, but the output schema carries that detail.

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 coverage is 100% and the single parameter's enum description already documents the savings→hysa and money-market→mma aliases, the full category list, the omit-for-all behavior, and the error/unavailable semantics. The description largely restates that text, adding little beyond the schema.

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 opens with a specific verb and resource: 'Return public data source freshness status and affected routes.' No sibling tool covers freshness, so the agent can immediately distinguish this from rate-listing tools like get_top_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 Guidelines4/5

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

It gives concrete invocation guidance—omit category for all sources, unknown categories error, known-but-empty sources are explicitly unavailable—plus a boundary caveat that source freshness does not imply an approved/current ranked deposit release. It stops short of naming when to prefer a sibling tool (e.g., call this before trusting get_top_hysa_rates), so it lacks explicit alternatives.

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

Deploy Server