SwitchWize MCP

CD Rollover Rules

get_cd_rollover_rules

Read-onlyIdempotent

Return verified CD rollover rules for one bank, or every bank SwitchWize has verified: what happens automatically at maturity if the customer does nothing, the grace period, how to stop the rollover, and the early-withdrawal penalty. Each fact is sourced directly from the bank's own disclosure; an unverified field is omitted, never guessed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`institutionId`	No	Optional institution_registry id, e.g. chase, american-express, wells-fargo. Omit to return every bank SwitchWize has verified.

Output Schema

TableJSON Schema

Name	Required	Description
`asOf`	No	ISO timestamp of the underlying data this response reflects.
`tool`	Yes
`count`	No
`error`	No
`sourceUrl`	No
`datasetUrl`	No
`attribution`	No
`generatedAt`	Yes	ISO timestamp this response was computed at.
`verified_at`	No
`institutions`	No
`institutionId`	No
`schemaVersion`	Yes
`methodologyUrl`	No
`freshnessStatus`	No
`gracePeriodDays`	No
`autoRenewDefault`	No
`autoRenewDescription`	No
`earlyWithdrawalPenalty`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026
- addedOutput schema / properties / error / properties / retryable
```
Added value: +{
+  "type": "boolean"
+}
```

Changed2 schema fields changedSep 17, 2026

addedOutput schema / properties

Added value: +{
+  "asOf": {
+    "description": "ISO timestamp of the underlying data this response reflects.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "attribution": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "autoRenewDefault": {
+    "type": [
+      "boolean",
+      "null"
+    ]
+  },
+  "autoRenewDescription": {
+    "type": "string"
+  },
+  "count": {
+    "type": "number"
+  },
+  "datasetUrl": {
+    "type": "string"
+  },
+  "earlyWithdrawalPenalty": {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "error": {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "suggestions": {
+        "items": {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "code",
+      "message"
+    ],
+    "type": "object"
+  },
+  "freshnessStatus": {
+    "enum": [
+      "fresh",
+      "aging",
+      "stale",
+      "unavailable"
+    ],
+    "type": "string"
+  },
+  "generatedAt": {
+    "description": "ISO timestamp this response was computed at.",
+    "type": "string"
+  },
+  "gracePeriodDays": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "institutionId": {
+    "type": "string"
+  },
+  "institutions": {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "methodologyUrl": {
+    "type": "string"
+  },
+  "schemaVersion": {
+    "type": "string"
+  },
+  "sourceUrl": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "tool": {
+    "type": "string"
+  },
+  "verified_at": {
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedOutput schema / required

Added value: +[
+  "schemaVersion",
+  "tool",
+  "generatedAt"
+]

Changed1 schema field changedSep 16, 2026

changedOutput schema / (root)

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

AddedSep 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds meaningful context beyond these: facts are sourced from the bank's own disclosure, and unverified fields are omitted rather than guessed. This clarifies the open-world nature of the tool without contradicting any annotation.

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 two sentences with no filler. It front-loads the core action and scope, then compresses the return-field enumeration and sourcing guarantee into the remaining text. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one optional parameter, a fully documented input schema, an output schema, and clear safety annotations, nothing needed to invoke the tool correctly is missing. The description also covers the epistemic contract (verified, sourced, never guessed), which is especially valuable for a lookup tool.

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 100%, and the schema already documents institutionId along with the omit-to-return-all behavior. The description largely restates this parameter guidance rather than adding new semantic detail, so the high-coverage baseline of 3 applies.

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 verified CD rollover rules') and precisely defines scope: one bank or every bank SwitchWize has verified. It also enumerates the specific fields returned, making the purpose unambiguous and clearly distinct from all 14 sibling tools, none of which target CD rollover rules.

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?

The description explains the main invocation branch (provide an institutionId or omit it to get all banks) but does not explicitly say when to choose this tool over alternatives or name a sibling it is not. Usage is implied by the tool's unique domain, but no explicit when-to-use or when-not-to-use guidance is given.

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.