Skip to main content
Glama

SwitchWize MCP

by io.github.switchwize
OverviewDiscussionsAdmin

Data Freshness

get_rate_freshness
Read-onlyIdempotent

Return public data source freshness status and affected routes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYes
errorNo
sourcesNo
attributionNo
generatedAtYesISO timestamp this response was computed at.
schemaVersionYes
affectedRoutesNo

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: +{
+  "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"
+]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  4. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the output content (freshness status and affected routes), which is useful but does not disclose other behavioral traits such as response format, potential time-sensitivity, or any dependency on external data. With annotations handling the main safety aspects, the description's additional value is moderate.

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, tightly-woven sentence that front-loads the primary action and result. It contains no filler or redundant phrasing, making it highly concise while still conveying the core purpose. The structure is appropriate for a tool with minimal complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although output schema exists (reducing the need to explain return values), the description leaves out essential context: it does not explain what 'category' refers to, what 'affected routes' means, or when an agent should invoke this tool relative to siblings. The tool's role in the broader workflow is unclear, making the definition incomplete for reliable agent use.

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

Parameters1/5

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

The input schema has one optional 'category' parameter with zero description coverage, and the description does not mention it at all. The agent has no idea what 'category' means, what values are acceptable, or how it affects the result. This is a critical omission because the tool's behavior is likely dependent on this parameter, and the description fails to compensate for the schema's silence.

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?

The description clearly states a specific action ('Return') and a precise resource ('public data source freshness status and affected routes'), which is distinct from all sibling tools that focus on rates, cards, or savings. The title 'Data Freshness' reinforces the purpose, making it easy for an agent to understand what this tool does without ambiguity.

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?

The description provides no guidance on when to use this tool versus the many siblings. It does not mention that it might be a prerequisite for checking data freshness before using other rate or card tools, nor does it state any exclusion criteria. An agent is left to infer the use case, which is a significant gap given the large sibling set.

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