Crypto Data & Market Analysis Agent

get_economic_calendar

Read-onlyIdempotent

Scheduled macro events (CPI, PCE, NFP / Employment Situation, GDP, Retail Sales, FOMC) from the official US release calendar. Call for upcoming economic catalysts. Returns the scheduled date and indicator, not analyst consensus.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	How many days ahead to cover, defaults to 14

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Scheduled macro releases ahead, soonest first.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "description": "Scheduled macro releases ahead, soonest first.",
+      "items": {
+        "properties": {
+          "actual": {
+            "description": "Null until the release lands.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "country": {
+            "type": "string"
+          },
+          "estimate": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "event": {
+            "type": "string"
+          },
+          "impact": {
+            "type": "string"
+          },
+          "previous": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "time": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "event",
+          "country",
+          "time",
+          "impact"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedAug 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds value beyond these by specifying the data source (official US release calendar) and clarifying that it returns 'scheduled date and indicator, not analyst consensus.' No contradictions 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 extremely concise: two sentences, front-loaded with examples, and no redundant information. Every word serves a purpose, earning its place.

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?

Given the tool's simplicity (one optional parameter, existing output schema, rich annotations), the description fully covers what the agent needs to know: what events are returned, what is not returned (consensus), and the source. No gaps remain.

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 100% for the single 'days' parameter, which already has a clear description. The tool description does not add additional meaning or constraints beyond what the schema provides, so baseline 3 is appropriate.

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 the tool returns scheduled macro events from the official US release calendar, listing specific indicators (CPI, PCE, NFP, GDP, etc.). It distinguishes itself from sibling tools which are mostly crypto-focused, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Call for upcoming economic catalysts,' providing clear usage context. It lacks explicit when-not-to-use or alternative guidance, but given the sibling set, this is the only macro calendar tool, so the usage is well implied.

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 tools Inspect

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

Need Help?