SwitchWize MCP

Official

by switchwize

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Data Freshness

get_rate_freshness

Read-onlyIdempotent

Check freshness status for public U.S. savings and rate comparison data sources, including affected routes. Flag stale or unavailable data before using comparisons.

Instructions

Return public data source freshness status and affected routes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`category`	No

Output Schema

TableJSON 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.

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

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds only that the output includes freshness status and affected routes; it says nothing about staleness thresholds, caching, or why 'openWorld' applies here.

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?

A single front-loaded sentence with no filler; the primary output is named first and the secondary output follows.

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?

The output schema exists, so return values need not be explained, and annotations cover safety. Still, the lone unexplained parameter and the undefined term 'affected routes' leave meaningful gaps for an agent deciding whether and how to call this health-check tool.

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?

The single optional 'category' parameter has 0% schema description coverage and no enum, and the description never references it. The 'public data source' phrasing only faintly hints that 'category' might scope the source type, leaving its meaning and valid values to inference.

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 and resource ('Return ... data source freshness status') plus a second output ('affected routes'), which sets it apart from the rate-fetching siblings. However, 'freshness status' and 'affected routes' remain loosely defined, so an agent knows the domain but not exactly what a 'route' is.

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 and no mention of any alternative. With 15 sibling tools all fetching or comparing rates, the description never says this is the metadata/health check to consult before trusting those results, nor any precondition for calling it.

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

Deploy Server