Skip to main content
Glama

SwitchWize MCP

Data Freshness

get_rate_freshness
Read-onlyIdempotent

Return public data source freshness status and affected routes. savings is an alias for hysa; money-market is an alias for mma. Also supports cds, checking, macro, bank-gap-index, and indices. Omit category for all supported sources. Unknown categories return an error; a source with no observations is explicitly unavailable. Source collection freshness does not establish that a ranked deposit release is approved or current.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional freshness category. savings maps to hysa; money-market maps to mma. Also supports cds, checking, macro, bank-gap-index, and indices. Omit for all supported sources. Unknown values return an error; a known source without observations is unavailable.

Output Schema

NameRequiredDescriptionDefault
toolYes
errorNo
sourceNoWhere the data comes from (URL).
sourcesNo
toolMetaNoVersion and stability of the tool that produced this reply. See /developers#tool-versions.
attributionNo
generatedAtYesISO timestamp this response was computed at.
schemaVersionYes
affectedRoutesNo

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. Changed2 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Optional freshness category. savings maps to hysa; money-market maps to mma. Also supports cds, checking, macro, bank-gap-index, and indices. Omit for all supported sources. Unknown values return an error; a known source without observations is unavailable."
    • addedInput schema / properties / category / enum
      Added value: +[
      +  "savings",
      +  "hysa",
      +  "cds",
      +  "money-market",
      +  "mma",
      +  "checking",
      +  "macro",
      +  "bank-gap-index",
      +  "indices"
      +]
  3. 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"
  4. Changed1 schema field changed
    • addedOutput schema / properties / error / properties / retryable
      Added value: +{
      +  "type": "boolean"
      +}
  5. Changed2 schema fields changed
    • addedOutput schema / properties
      Added value: +{
      +  "affectedRoutes": {
      +    "items": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "attribution": {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  "error": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "code": {
      +        "type": "string"
      +      },
      +      "message": {
      +        "type": "string"
      +      },
      +      "suggestions": {
      +        "items": {
      +          "additionalProperties": true,
      +          "type": "object"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "code",
      +      "message"
      +    ],
      +    "type": "object"
      +  },
      +  "generatedAt": {
      +    "description": "ISO timestamp this response was computed at.",
      +    "type": "string"
      +  },
      +  "schemaVersion": {
      +    "type": "string"
      +  },
      +  "sources": {
      +    "items": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "tool": {
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / required
      Added value: +[
      +  "schemaVersion",
      +  "tool",
      +  "generatedAt"
      +]
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  7. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world. The description adds genuine behavioral detail beyond them: error behavior for unknown categories, the explicit unavailable state for known-but-empty sources, and a caveat that collection freshness does not imply an approved/current ranked deposit release. That caveat is real context an agent could otherwise misread.

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-loads the purpose, then packs alias and error semantics efficiently. Slightly repetitive of the schema and the final caveat sentence is dense, but every sentence carries information.

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?

One optional enum param, full schema coverage, and an output schema so return shape needs no explanation. The description covers the remaining unknowns an agent needs: aliasing, all-sources behavior, error vs unavailable distinction, and the freshness-vs-approval caveat.

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 100% and the enum already documents every alias mapping (savings→hysa, money-market→mma) and the omit/unknown semantics. The description largely restates the schema's param text, so it adds little beyond structured data. Baseline 3 applies.

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: 'Return public data source freshness status and affected routes.' The 'affected routes' clause signals this is a diagnostic/status tool rather than a rate query, which distinguishes it from rate-listing siblings like get_top_rates. It does not explicitly contrast with any named sibling, keeping it at 4 rather than 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?

Gives clear invocation guidance for the single parameter ('Omit category for all supported sources', unknown categories error out), but gives no indication of when an agent should call this versus the many rate/data siblings. Usage is implied by the freshness framing rather than stated as a decision rule.

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.