Skip to main content
Glama

SwitchWize MCP

Bank Gap Index

get_bank_gap_index
Read-onlyIdempotent

Return the current SwitchWize Bank Gap Index headline value, latest release, and methodology URL.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
asOfNoISO timestamp of the underlying data this response reflects.
toolYes
errorNo
labelNo
monthNo
sourceNoWhere the data comes from (URL).
index_idNo
toolMetaNoVersion and stability of the tool that produced this reply. See /developers#tool-versions.
gapPointsNo
topAvgApyNo
datasetUrlNo
attributionNo
generatedAtYesISO timestamp this response was computed at.
verified_atNo
banksTrackedNo
headlineValueNo
schemaVersionYes
methodologyUrlNo
nationalAvgApyNo
freshnessStatusNo
releaseArchiveUrlNo

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"
      +  },
      +  "banksTracked": {
      +    "type": [
      +      "number",
      +      "null"
      +    ]
      +  },
      +  "datasetUrl": {
      +    "type": "string"
      +  },
      +  "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"
      +  },
      +  "gapPoints": {
      +    "type": [
      +      "number",
      +      "null"
      +    ]
      +  },
      +  "generatedAt": {
      +    "description": "ISO timestamp this response was computed at.",
      +    "type": "string"
      +  },
      +  "headlineValue": {
      +    "type": [
      +      "number",
      +      "null"
      +    ]
      +  },
      +  "index_id": {
      +    "type": "string"
      +  },
      +  "label": {
      +    "type": "string"
      +  },
      +  "methodologyUrl": {
      +    "type": "string"
      +  },
      +  "month": {
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "nationalAvgApy": {
      +    "type": [
      +      "number",
      +      "null"
      +    ]
      +  },
      +  "releaseArchiveUrl": {
      +    "type": "string"
      +  },
      +  "schemaVersion": {
      +    "type": "string"
      +  },
      +  "tool": {
      +    "type": "string"
      +  },
      +  "topAvgApy": {
      +    "type": [
      +      "number",
      +      "null"
      +    ]
      +  },
      +  "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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds that this is a 'current' snapshot with a 'latest release' pointer and a methodology URL, which is mild but real context about freshness and provenance. It does not mention caching, refresh cadence, or the open-world external-fetch implication.

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?

A single sentence with no waste, and the resource identity plus returned fields are front-loaded. Every clause (headline value, latest release, methodology URL) carries information.

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 and annotations cover safety and idempotency, so return-value detail need not be repeated. What is missing is only sibling differentiation against get_bank_gap, which is the one thing an agent must resolve to invoke the right tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a no-argument, single-shot retrieval rather than inviting any filtering.

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 ('Return') and a specific resource (SwitchWize Bank Gap Index), plus the exact fields returned: headline value, latest release, methodology URL. However, it does not distinguish itself from the sibling get_bank_gap or get_index_dataset, which plausibly cover overlapping ground, so an agent cannot confidently choose without opening schemas.

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 when-to-use or when-not-to-use guidance. With siblings named get_bank_gap and get_index_dataset in the same family, the description gives no signal about whether this is the headline-only variant or when an agent should prefer it over those alternatives.

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.