Skip to main content
Glama

SwitchWize MCP

Compare Savings Rates

compare_switch_savings
Read-onlyIdempotent

Compare a user's current APY with SwitchWize's current top savings APY for a balance.

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": {
      "currentApy": "<currentApy>"
    },
    "name": "compare_switch_savings"
  }
}

Input Schema

NameRequiredDescriptionDefault
balanceNo
currentApyYes

Output Schema

NameRequiredDescriptionDefault
asOfNoISO timestamp of the underlying data this response reflects.
toolYes
errorNo
sourceNoWhere the data comes from (URL).
balanceNo
toolMetaNoVersion and stability of the tool that produced this reply. See /developers#tool-versions.
annualGapNo
currentApyNo
attributionNo
generatedAtYesISO timestamp this response was computed at.
verified_atNo
comparisonApyNo
schemaVersionYes
methodologyUrlNo
currentInterestNo
freshnessStatusNo
breakEvenFramingNo
comparisonInterestNo
recommendationStatusNo

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. Changed7 schema fields changed
    • changedOutput schema / properties / annualGap / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / comparisonApy / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / comparisonInterest / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
    • 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"
    • addedOutput schema / properties / recommendationStatus
      Added value: +{
      +  "enum": [
      +    "comparison_available",
      +    "data_unavailable"
      +  ],
      +  "type": "string"
      +}
  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: +{
      +  "annualGap": {
      +    "type": "number"
      +  },
      +  "asOf": {
      +    "description": "ISO timestamp of the underlying data this response reflects.",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "attribution": {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  "balance": {
      +    "type": "number"
      +  },
      +  "breakEvenFraming": {
      +    "type": "string"
      +  },
      +  "comparisonApy": {
      +    "type": "number"
      +  },
      +  "comparisonInterest": {
      +    "type": "number"
      +  },
      +  "currentApy": {
      +    "type": "number"
      +  },
      +  "currentInterest": {
      +    "type": "number"
      +  },
      +  "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"
      +  },
      +  "methodologyUrl": {
      +    "type": "string"
      +  },
      +  "schemaVersion": {
      +    "type": "string"
      +  },
      +  "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. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds useful context that the comparison benchmark is SwitchWize's live top rate (open-world fetch) and that the result is scoped to a balance, but it does not say what happens when balance is omitted or how APY values are interpreted.

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?

One sentence, front-loaded with the verb and both operands, with zero filler. Nothing in it is redundant with structured fields or padding.

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-value explanation is not needed, and the annotations cover the safety profile. The remaining gap is that with two undocumented params and exactly one required, the description never states that balance is optional or what the comparison yields when it is absent.

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 0%, so the description bears real weight here; it does clarify that currentApy means the user's own APY and that balance drives the comparison. However, it leaves the unit convention ambiguous (percent vs decimal for a 0-25 bounded field) and does not explain the optionality or default behavior of balance, which are the most likely invocation errors.

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 (compare) and two specific resources (user's current APY vs SwitchWize's top savings APY), with the balance as the computation basis. It is clear on its own, but it never distinguishes itself from close siblings like compare_accounts or get_top_hysa_rates, so an agent cannot route between them on this text alone.

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?

There is no explicit when-to-use or when-not-to-use statement, and none of the many sibling tools (compare_accounts, get_top_hysa_rates, best_move_this_week) are referenced as alternatives. The agent must infer from the tool name that this is the 'what would I gain by switching' calculation.

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.