Skip to main content
Glama

SwitchWize MCP

High-Yield Savings Rates

get_top_hysa_rates
Read-onlyIdempotent

Return top high-yield savings rates with freshness and attribution. Answers only from the editor-approved snapshot; before its first release it returns no ranked rates and says so (approval_status: not_yet_approved). approvedOnly makes the requirement explicit. detail=full adds every listed account marked verified or tracked, best picks, movers, history and a headline summary.

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_top_hysa_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.
approvedOnlyNoRequire an editor-approved HYSA snapshot. The default tool already answers only from the approved release; before its first release it returns no ranked rates (approval_status: not_yet_approved).

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. 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"
      +}
  3. 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"
      +]
  4. Changed2 schema fields changed
    • addedInput schema / properties / approvedOnly
      Added value: +{
      +  "description": "Require an editor-approved HYSA snapshot. The default tool already answers only from the approved release; before its first release it returns no ranked rates (approval_status: not_yet_approved).",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / dataStatus
      Added value: +{
      +  "enum": [
      +    "available",
      +    "no_observations",
      +    "no_eligible_rates",
      +    "source_error",
      +    "unavailable",
      +    "stale",
      +    "conflicted"
      +  ],
      +  "type": "string"
      +}
  5. 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"
      +]
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  7. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the gated-release lifecycle: before the first editor-approved snapshot it returns no ranked rates and reports approval_status: not_yet_approved. That empty-state behavior is exactly the kind of thing an agent cannot infer from schema or annotations. It stops short of describing rate limits, ordering, or how 'freshness and attribution' are surfaced in the payload.

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?

Front-loaded with the core action and the empty-state caveat early, and the detail-mode expansion is compact. The sentence 'approvedOnly makes the requirement explicit' is mild redundancy given the preceding sentence already stated the gate.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description covers the two things an agent would otherwise get wrong: the not-yet-approved empty state and the summary-vs-full payload difference. Missing only limit semantics and any sibling routing.

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?

With 67% schema description coverage, the schema already carries the detail-mode semantics and the approvedOnly gate nearly verbatim, so the description largely restates them ('detail=full adds every listed account...'). The limit parameter (1-25) is left unexplained in both places, which is the one genuine gap.

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+resource ('Return top high-yield savings rates') and adds the freshness/attribution framing, so the agent knows it is a ranked-rate retrieval, not a comparison or calculator. However, it never names the obvious sibling get_top_rates (or compare_switch_savings), so the agent must infer the HYSA-vs-other-products split from the name alone.

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 only implied: the description says what it answers from and what detail=full adds, which suggests 'use this for a ranked HYSA list.' It never states when to prefer a sibling such as get_top_rates, compare_accounts, or compare_switch_savings, and gives no exclusions.

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.