Skip to main content
Glama

SwitchWize MCP

by io.github.switchwize
OverviewDiscussionsAdmin

Bank Gap Index

get_bank_gap_index
Read-onlyIdempotent

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
asOfNoISO timestamp of the underlying data this response reflects.
toolYes
errorNo
labelNo
monthNo
index_idNo
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. Changed1 schema field changed
    • addedOutput schema / properties / error / properties / retryable
      Added value: +{
+  "type": "boolean"
+}
  2. 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"
+]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds context by specifying the exact return contents (value, release, URL), which goes beyond the annotations. No behavioral caveats or side effects are disclosed, but none are expected for a read-only query.

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 concise, front-loaded sentence that immediately states the action and the exact outputs. No filler or redundancy; every phrase earns its place.

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?

For a parameterless read-only tool with a pre-existing output schema, the description is sufficient. It names all three returned components, and the output schema handles structure. Nothing an agent needs to call it correctly is missing.

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

Parameters5/5

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

The tool has zero parameters, and schema coverage is trivially 100%. The description explicitly states it returns the current value, reinforcing that no input is required. Baseline for 0 params is 4, but the description adds clarity that there is nothing to configure, so a 5 is warranted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Return) and resource (SwitchWize Bank Gap Index) with clear scope (headline value, latest release, methodology URL). Distinct from siblings like get_bank_gap, which likely provides more detailed data, and get_index_dataset, which may return a full dataset.

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?

No guidance on when to use this tool over alternatives. It does not mention exclusions or when to prefer it over get_bank_gap, get_index_dataset, or get_rate_freshness. Usage is only implied by the tool name and description, but no explicit routing advice is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SwitchWize MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources