Skip to main content
Glama

SwitchWize MCP

Top Rates

get_top_rates
Read-onlyIdempotent

Return top SwitchWize rates with freshness and attribution. Savings, CDs, checking and money market answer only from their editor-approved snapshot. A category with no approved release yet returns no ranked rates and says so (approval_status: not_yet_approved) rather than serving unverified observations; approvedOnly makes that requirement explicit. Approved responses include product terms and field evidence; stale or unavailable releases return no ranked rates. detail=full (savings) adds the complete shared build: every listed account marked verified or tracked, best picks, movers, history and a headline summary.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "get_top_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
detailNosummary (default) adds list_counts. full (savings) adds the complete shared build: accounts (verified and tracked, each marked), best_picks, movers, history and summary. rates stays verified-only either way.
categoryYesU.S. deposit category: savings (alias hysa), cds, money-market (alias mma), or checking.
approvedOnlyNoRequire an editor-approved deposit snapshot. Savings, CDs, checking and money market always answer from their own approved release; a category with no release yet returns no ranked rates (approval_status: not_yet_approved), as do stale or unavailable releases.

Output Schema

NameRequiredDescriptionDefault
idNo
asOfNo
toolNo
countNo
errorNo
ratesNo
termsNo
sourceNo
categoryNo
toolMetaNoVersion and stability of the tool that produced this reply. See /developers#tool-versions.
rate_typeNo
releaseIdNo
dataStatusNo
attributionNo
emptyReasonNo
generatedAtYes
releaseSizeNo
releaseStatusNo
schemaVersionYes
sourceDetailsNo
methodologyUrlNo
freshnessStatusNo
attributionDetailsNo
supportedCategoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Rate category, e.g. savings, cds, money-market, checking, mortgage."New value: +"U.S. deposit category: savings (alias hysa), cds, money-market (alias mma), or checking."
    • addedInput schema / properties / category / enum
      Added value: +[
      +  "savings",
      +  "hysa",
      +  "cds",
      +  "money-market",
      +  "mma",
      +  "checking"
      +]
  3. Changed3 schema fields changed
    • addedOutput schema / properties / releaseId
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / releaseSize
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / releaseStatus
      Added value: +{
      +  "enum": [
      +    "observed",
      +    "unavailable"
      +  ],
      +  "type": "string"
      +}
  4. Changed7 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "summary (default) adds list_counts. full (savings) adds the complete shared build: accounts (verified and tracked, each marked), best_picks, movers, history and summary. rates stays verified-only either way.",
      +  "enum": [
      +    "summary",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "properties": {
      +      "attribution": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "category",
      +      "count",
      +      "freshnessStatus",
      +      "rates"
      +    ]
      +  },
      +  {
      +    "properties": {
      +      "attribution": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      }
      +    },
      +    "required": [
      +      "tool",
      +      "error",
      +      "attribution"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / attribution / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties / attribution / type
      Removed value: -"string"
    • addedOutput schema / properties / error
      Added value: +{
      +  "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"
      +}
    • addedOutput schema / properties / tool
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "schemaVersion",
      -  "category",
      -  "count",
      -  "generatedAt",
      -  "freshnessStatus",
      -  "rates"
      -]New value: +[
      +  "schemaVersion",
      +  "generatedAt"
      +]
  5. Changed2 schema fields changed
    • addedInput schema / properties / approvedOnly
      Added value: +{
      +  "description": "Require an editor-approved deposit snapshot. Savings, CDs, checking and money market always answer from their own approved release; a category with no release yet returns no ranked rates (approval_status: not_yet_approved), as do stale or unavailable releases.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / dataStatus
      Added value: +{
      +  "enum": [
      +    "available",
      +    "no_observations",
      +    "no_eligible_rates",
      +    "source_error",
      +    "unavailable",
      +    "stale",
      +    "conflicted"
      +  ],
      +  "type": "string"
      +}
  6. Changed2 schema fields changed
    • 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"
      +]
  7. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  8. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description's real contribution is behavioral: no ranked rates on unapproved/stale releases, an approval_status: not_yet_approved marker, and the contents of detail=full. That is meaningful context beyond structured fields, though it doesn't address rate limits or auth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, but the middle is dense and partly redundant — the stale/unavailable-returns-no-rates point is made twice, and detail=full is restated almost verbatim from the schema. It reads as a spec dump rather than tight guidance.

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?

With an output schema present, the description needn't explain return shapes, yet it still summarizes the full build contents. Combined with the approval and staleness rules, an agent has enough to call it correctly; only the limit parameter and sibling disambiguation remain unaddressed.

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

Parameters4/5

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

Schema coverage is 75% and the description reinforces the semantics of category, approvedOnly, and detail=full with consequences (what happens when no release exists). Only limit is left unexplained in both description and schema, which is a minor gap given min/max bounds exist.

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 top SwitchWize rates") plus the two things it guarantees: freshness and attribution. It also enumerates the covered categories. It never names or distinguishes itself from the near-identical sibling get_top_hysa_rates, so an agent choosing between them gets no help.

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?

Usage is implied rather than prescribed: the description explains what happens under approval/staleness conditions, which implies when the tool is appropriate, but never says when to pick this over get_top_hysa_rates, get_rate_freshness, or compare_accounts. No explicit alternatives or exclusions are given.

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.