Skip to main content
Glama

SwitchWize MCP

by io.github.switchwize
OverviewDiscussionsAdmin

Index Dataset

get_index_dataset
Read-onlyIdempotent

Return a SwitchWize index dataset summary and recent series.

Input Schema

NameRequiredDescriptionDefault
limitNo
indexIdYesIndex id, e.g. bank-gap-index, cd-spread, mma-spread, checking-gap.

Output Schema

NameRequiredDescriptionDefault
asOfNoISO timestamp of the underlying data this response reflects.
toolYes
errorNo
labelNo
seriesNo
index_idNo
attributionNo
generatedAtYesISO timestamp this response was computed at.
verified_atNo
schemaVersionYes
methodologyUrlNo
freshnessStatusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Changed1 schema field changed
    • addedOutput schema / properties / error / properties / retryable
      Added value: +{
+  "type": "boolean"
+}
  3. 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"
+  },
+  "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"
+  },
+  "index_id": {
+    "type": "string"
+  },
+  "label": {
+    "type": "string"
+  },
+  "methodologyUrl": {
+    "type": "string"
+  },
+  "schemaVersion": {
+    "type": "string"
+  },
+  "series": {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "tool": {
+    "type": "string"
+  },
+  "verified_at": {
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "schemaVersion",
+  "tool",
+  "generatedAt"
+]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  5. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so the safety and idempotency profile is covered. The description adds that it returns a 'summary and recent series,' which hints at output shape but doesn't specify pagination, rate limits, or what 'recent' means. With annotations already conveying core behavior, this is adequate but not rich.

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?

It's a single, efficient sentence with no fluff, though it could be slightly more front-loaded by leading with the action and result. No wasted words.

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

Completeness3/5

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

An output schema exists, so return values needn't be explained. However, for a tool with siblings that serve similar purposes, the description lacks the routing information needed to pick this tool correctly. The parameter gap (undocumented 'limit') also leaves an incompleteness.

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 coverage is 50%. The indexId parameter has a description with examples in the schema; the limit parameter has no description in the schema or in the description text. The description doesn't compensate for the missing limit documentation. Baseline 3 is appropriate when schema partially covers parameters.

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

Purpose3/5

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

The description states a verb and resource: 'Return a SwitchWize index dataset summary and recent series.' This is clear enough to understand the tool's output, but it doesn't distinguish it from siblings like get_bank_gap_index or get_bank_gap. An agent could confuse this generic 'index dataset' tool with those specific index tools.

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 when-to-use guidance is provided. It doesn't mention alternatives, conditions, or exclusions. With many similar-sounding sibling tools, this omission is significant.

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