Skip to main content
Glama

Crypto Data & Market Analysis Agent

by app.vercel.asistent-crypto
OverviewDiscussionsAdmin

get_macro_rates

Read-onlyIdempotent

Live US macro data with the derived signals, not just the raw levels: Fed funds rate, 2Y and 10Y Treasury yields plus the 2s10s YIELD CURVE SPREAD (with its direction — steepening or flattening — and an inverted flag), CPI inflation year-over-year, the broad trade-weighted dollar index (a different index from the ICE dollar index, so read its direction rather than comparing its level), VIX and M2 money supply. Every series carries its previous reading, so direction is available without a second call. The curve slope, not the level of any single yield, is the liquidity and cycle signal: inversion has preceded every US recession, and re-steepening out of an inversion usually marks the start of easing — the moment that matters for risk assets. VIX explains crypto drawdowns that have no crypto-native cause.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
m2No
vixNo
ust2yNo
cpiYoYNo
ust10yNo
fedFundsNo
dollarIndexNo
yieldCurve2s10sNo10Y minus 2Y. Inversion has preceded every recent US recession.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedOutput schema / properties / cpiYoY / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / dollarIndex / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / fedFunds / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / m2 / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / ust10y / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / ust2y / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / vix / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / yieldCurve2s10s / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "cpiYoY": {
+      "properties": {
+        "date": {
+          "description": "ISO date of the observation.",
+          "type": "string"
+        },
+        "previous": {
+          "description": "Prior observation, for direction.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "value": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "value",
+        "date"
+      ],
+      "type": "object"
+    },
+    "dollarIndex": {
+      "properties": {
+        "date": {
+          "description": "ISO date of the observation.",
+          "type": "string"
+        },
+        "previous": {
+          "description": "Prior observation, for direction.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "value": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "value",
+        "date"
+      ],
+      "type": "object"
+    },
+    "fedFunds": {
+      "properties": {
+        "date": {
+          "description": "ISO date of the observation.",
+          "type": "string"
+        },
+        "previous": {
+          "description": "Prior observation, for direction.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "value": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "value",
+        "date"
+      ],
+      "type": "object"
+    },
+    "m2": {
+      "properties": {
+        "date": {
+          "description": "ISO date of the observation.",
+          "type": "string"
+        },
+        "previous": {
+          "description": "Prior observation, for direction.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "value": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "value",
+        "date"
+      ],
+      "type": "object"
+    },
+    "ust10y": {
+      "properties": {
+        "date": {
+          "description": "ISO date of the observation.",
+          "type": "string"
+        },
+        "previous": {
+          "description": "Prior observation, for direction.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "value": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "value",
+        "date"
+      ],
+      "type": "object"
+    },
+    "ust2y": {
+      "properties": {
+        "date": {
+          "description": "ISO date of the observation.",
+          "type": "string"
+        },
+        "previous": {
+          "description": "Prior observation, for direction.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "value": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "value",
+        "date"
+      ],
+      "type": "object"
+    },
+    "vix": {
+      "properties": {
+        "date": {
+          "description": "ISO date of the observation.",
+          "type": "string"
+        },
+        "previous": {
+          "description": "Prior observation, for direction.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "value": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "value",
+        "date"
+      ],
+      "type": "object"
+    },
+    "yieldCurve2s10s": {
+      "description": "10Y minus 2Y. Inversion has preceded every recent US recession.",
+      "properties": {
+        "direction": {
+          "enum": [
+            "steepening",
+            "flattening",
+            "flat",
+            null
+          ],
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "inverted": {
+          "type": "boolean"
+        },
+        "previous": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "value": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "value",
+        "inverted"
+      ],
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4/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. The description adds context about derived signals (yield curve spread, VIX explanation) which aids understanding of the data's meaning and behavior, going beyond the raw annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and somewhat redundant, repeating the 'derived signals' concept and elaborating on the yield curve and VIX details. It could be more concise while retaining key information.

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?

Given no parameters and no output schema, the description effectively lists the data points returned and explains their relevance. It is sufficiently complete for a read-only data fetch tool, though it omits potential error or edge-case details.

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

Parameters4/5

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

The tool has zero parameters, so there is nothing to explain. The description provides no parameter info, but that is appropriate since none exist; the baseline for 0 params is 4.

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 it provides live US macro data with derived signals (Fed funds rate, yields, CPI, dollar index, VIX, M2). It distinguishes from sibling get_* tools by focusing on macro rates, which is a unique topic.

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?

No explicit guidance on when to use this tool over alternatives, though the distinct subject matter makes it implicitly obvious. It lacks a direct 'use this for macro data' or comparisons to other tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crypto Data & Market Analysis Agent 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