Skip to main content
Glama

SwitchWize MCP

Bank Savings Gap

get_bank_gap
Read-onlyIdempotent

Estimate annual savings interest forgone for a supplied balance and optional bank name. comparisonApy is the average of the top three tracked savings rates, not an average across all banks; bankCount is the size of the tracked set. baselineApy is the named bank's APY, or the national savings benchmark when no bank is supplied. Return annualGap, APYs, observation date, freshness and methodology. This is a hypothetical estimate, not guaranteed savings or an account recommendation; verify eligibility, fees and current provider terms.

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_bank_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankNoOptional bank name for user-facing context.
balanceNo

Output Schema

NameRequiredDescriptionDefault
asOfNoISO timestamp of the underlying data this response reflects.
bankNo
toolYes
errorNo
sourceNoWhere the data comes from (URL).
balanceNo
bankApyNo
toolMetaNoVersion and stability of the tool that produced this reply. See /developers#tool-versions.
annualGapNo
bankCountNoNumber of tracked banks in the comparison set, not the number averaged into comparisonApy.
attributionNo
baselineApyNoNamed bank APY, or national savings benchmark when no bank is supplied. Percentage units.
generatedAtYesISO timestamp this response was computed at.
verified_atNo
comparisonApyNoAverage of the top three tracked savings rates (or all available rates if fewer than three). Not an average across bankCount banks. Percentage units.
schemaVersionYes
methodologyUrlNo
freshnessStatusNo

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. Changed6 schema fields changed
    • addedOutput schema / properties / bankCount / description
      Added value: +"Number of tracked banks in the comparison set, not the number averaged into comparisonApy."
    • addedOutput schema / properties / baselineApy / description
      Added value: +"Named bank APY, or national savings benchmark when no bank is supplied. Percentage units."
    • addedOutput schema / properties / comparisonApy / description
      Added value: +"Average of the top three tracked savings rates (or all available rates if fewer than three). Not an average across bankCount banks. Percentage units."
    • 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: +{
      +  "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"
      +  },
      +  "bank": {
      +    "type": [
      +      "object",
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "bankApy": {
      +    "type": [
      +      "number",
      +      "null"
      +    ]
      +  },
      +  "bankCount": {
      +    "type": "number"
      +  },
      +  "baselineApy": {
      +    "type": "number"
      +  },
      +  "comparisonApy": {
      +    "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

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, and the description goes beyond them by disclosing the methodology: comparisonApy is the average of the top three tracked rates (not all banks), bankCount is the tracked-set size, and baselineApy falls back to a national benchmark when no bank is given. It also flags the result as a hypothetical estimate with a verification caveat. Minor gap: no statement about data vintage beyond a returned observation date.

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?

Four sentences, front-loaded with the purpose, then methodology, then the deliverable list, then the disclaimer. Dense but each sentence carries information. Slight redundancy in enumerating return fields when an output schema already exists.

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 an output schema present, the description need not explain return values, and it still names the headline fields. For a two-parameter, read-only estimation tool it covers the calculation basis, the fallback behavior, and the interpretation caveat — everything an agent needs to call and characterize the result correctly.

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 only 50% — 'balance' has no description at all — but the description compensates by explaining what each parameter does to the result: balance drives the forgone-interest figure, and bank selects whether baselineApy is the named bank's APY or the national benchmark. That is meaning beyond the schema, though the balance units and rounding are still unstated.

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: 'Estimate annual savings interest forgone for a supplied balance and optional bank name.' An agent can tell this is a per-user gap calculation rather than a raw rate listing. It does not explicitly distinguish itself from close siblings such as get_bank_gap_index or get_reality_score, so it falls short of a 5.

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 by the definition of the inputs — supply a balance to compute a gap, optionally a bank to change the baseline. There is no explicit when-to-use/when-not-to-use statement and no named alternative, so the agent must infer routing from the sibling list on its own.

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.