Skip to main content
Glama

SwitchWize MCP

by io.github.switchwize
OverviewDiscussionsAdmin

Reward Valuations

get_reward_valuations
Read-onlyIdempotent

Return SwitchWize points/miles valuations (cents per point) per reward currency, with sample size and provisional/published status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyNoOptional reward currency id or name, e.g. chase-ultimate-rewards or Membership Rewards.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
asOfNoISO timestamp of the underlying data this response reflects.
toolYes
countNo
errorNo
datasetUrlNo
valuationsNo
attributionNo
generatedAtYesISO timestamp this response was computed at.
verified_atNo
schemaVersionYes
methodologyUrlNo
freshnessStatusNo

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"
+  },
+  "count": {
+    "type": "number"
+  },
+  "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"
+  },
+  "generatedAt": {
+    "description": "ISO timestamp this response was computed at.",
+    "type": "string"
+  },
+  "methodologyUrl": {
+    "type": "string"
+  },
+  "schemaVersion": {
+    "type": "string"
+  },
+  "tool": {
+    "type": "string"
+  },
+  "valuations": {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "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. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, so the description does not need to restate that. It adds useful context beyond the annotations by mentioning that results include sample size and provisional/published status, which helps an agent assess data reliability. No contradiction with annotations.

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 dense sentence with no filler. The action and resource are front-loaded, followed by useful qualifiers like units and status fields, making it easy to scan.

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 simple read-only lookup with one optional parameter, rich annotations, and an output schema, the description is complete. An agent knows what the tool returns, how to filter it, and what reliability signals to expect.

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?

The input schema already documents the single optional 'currency' parameter at 100% coverage, so the description does not need to repeat format details. The description adds only mild domain framing—'per reward currency'—without enriching parameter behavior beyond what the schema provides.

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 uses a specific verb ('Return') and names the exact resource ('SwitchWize points/miles valuations') with units ('cents per point') and key fields ('sample size and provisional/published status'). This clearly distinguishes it from sibling tools focused on bank rates, card offers, or index data.

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?

The description implies when to use this tool—when reward-currency valuation data is needed—but provides no explicit when-to-use versus alternative guidance. None of the sibling tools are close enough to cause confusion, so this is a minor gap rather than a misleading one.

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