Skip to main content
Glama

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cd_rollover_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
institutionIdNoOptional institution_registry id, e.g. chase, american-express, wells-fargo. Omit to return every bank SwitchWize has verified.

Output Schema

NameRequiredDescriptionDefault
asOfNoISO timestamp of the underlying data this response reflects.
toolYes
countNo
errorNo
sourceNoWhere the data comes from (URL).
toolMetaNoVersion and stability of the tool that produced this reply. See /developers#tool-versions.
sourceUrlNo
datasetUrlNo
attributionNo
generatedAtYesISO timestamp this response was computed at.
verified_atNo
institutionsNo
institutionIdNo
schemaVersionYes
methodologyUrlNo
freshnessStatusNo
gracePeriodDaysNo
autoRenewDefaultNo
autoRenewDescriptionNo
earlyWithdrawalPenaltyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / source
      Added value: +{
      +  "description": "Where the data comes from (URL).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / toolMeta
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Version and stability of the tool that produced this reply. See /developers#tool-versions.",
      +  "properties": {
      +    "changelogUrl": {
      +      "type": "string"
      +    },
      +    "stability": {
      +      "enum": [
      +        "stable",
      +        "beta"
      +      ],
      +      "type": "string"
      +    },
      +    "version": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • removedOutput schema / properties / error / properties / suggestions / items / additionalProperties
      Removed value: -true
    • addedOutput schema / properties / error / properties / suggestions / items / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties / error / properties / suggestions / items / type
      Removed value: -"object"
  3. Changed1 schema field changed
    • addedOutput schema / properties / error / properties / retryable
      Added value: +{
      +  "type": "boolean"
      +}
  4. Changed2 schema fields changed
    • 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"
      +]
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  6. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: every fact is sourced from the bank's own disclosure and unverified fields are omitted rather than guessed, warning the agent that responses can have missing keys. It stops short of describing coverage limits per institution or freshness.

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?

Two sentences, no filler, with scope stated before the provenance caveat. The first sentence is dense with a comma-list but every item earns its place by telling the agent what a call actually returns.

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 a single optional parameter, an output schema, and annotations carrying the safety profile, the description covers everything an agent needs: scope selection, what facts come back, and the omission-on-unverified rule that shapes how results should be read.

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 parameter already documents the id format and the omit-for-all-banks behavior. The description's 'one bank, or every bank' restates the same semantics without adding format or edge-case detail, so the 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?

States a specific verb and resource ('Return verified CD rollover rules') and immediately enumerates the exact facts returned: automatic maturity action, grace period, how to stop rollover, and early-withdrawal penalty. No sibling tool covers CD rollover mechanics, and the enumeration makes the boundary obvious without opening a schema.

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?

The description makes the scope switch explicit: one bank by id, or all verified banks when the id is omitted, which is the main selection decision for this tool. It gives clear context for when the tool applies but names no exclusions or alternative tools for overlapping questions (e.g. rate comparison siblings).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.