Skip to main content
Glama

SwitchWize MCP

by io.github.switchwize
OverviewDiscussionsAdmin

High-Yield Savings Rates

get_top_hysa_rates
Read-onlyIdempotent

Return top high-yield savings rates with freshness and attribution metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
asOfNo
countYes
ratesYes
termsNo
sourceNo
categoryYes
rate_typeNo
attributionNo
emptyReasonNo
generatedAtYes
schemaVersionYes
sourceDetailsNo
methodologyUrlNo
freshnessStatusYes
attributionDetailsNo
supportedCategoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties
      Added value: +{
+  "asOf": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "attribution": {
+    "type": "string"
+  },
+  "attributionDetails": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "category": {
+    "type": "string"
+  },
+  "count": {
+    "type": "number"
+  },
+  "emptyReason": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "freshnessStatus": {
+    "enum": [
+      "fresh",
+      "aging",
+      "stale",
+      "unavailable"
+    ],
+    "type": "string"
+  },
+  "generatedAt": {
+    "type": "string"
+  },
+  "id": {
+    "type": "string"
+  },
+  "methodologyUrl": {
+    "type": "string"
+  },
+  "rate_type": {
+    "enum": [
+      "APY",
+      "APR"
+    ],
+    "type": "string"
+  },
+  "rates": {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "schemaVersion": {
+    "type": "string"
+  },
+  "source": {
+    "type": "string"
+  },
+  "sourceDetails": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "supportedCategories": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "terms": {
+    "type": "string"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "schemaVersion",
+  "category",
+  "count",
+  "generatedAt",
+  "freshnessStatus",
+  "rates"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description does not need to restate those. It adds useful context that results include freshness and attribution metadata. However, it does not disclose default behavior when the optional limit parameter is omitted, which is a minor transparency gap.

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?

The description is a single, front-loaded sentence with no filler. Every word adds meaning: returning data, specifying the domain, and noting metadata.

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?

For a tool with one optional parameter, an output schema, and strong safety annotations, the description covers the core purpose and result characteristics. The only notable omission is the default behavior of the limit parameter, but this is a minor gap given the simplicity of the tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to compensate for parameter semantics, but it does not mention the limit parameter at all. The schema provides type and min/max constraints, but no meaning or default behavior. Since the limit is optional, the agent is left to infer it controls result count without guidance on default.

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?

The description uses a clear verb ('Return') and a specific resource ('top high-yield savings rates'), and it adds the metadata qualifier 'freshness and attribution'. This distinguishes it from the generic sibling get_top_rates, though it does not explicitly name or contrast that sibling.

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 implied through the tool name and description: an agent should call this when the request involves top high-yield savings rates. However, there is no explicit guidance about when to use this tool versus alternatives like get_top_rates or get_rate_freshness, and no when-not-to-use conditions.

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