MoveSurge

Economic data and calendar

economic_data

Read-only

Released economic data (CPI, payrolls, PMIs, central-bank decisions and more) with actual vs forecast vs previous, the surprise direction and the measured market reaction in the minutes after the release; plus the scheduled releases ahead. Defaults to high-impact releases. Use for 'what did CPI come in at and how did markets react' or 'what data is out this week'.

Input Schema

Name	Required	Description
`hours`	No	Look back 1-1440 hours; default 48. Actual coverage is disclosed in archive_coverage.
`limit`	No	Max rows per list (1-50, default 20).
`query`	No	Up to eight title words, e.g. CPI, payrolls, or retail sales. Filters both released and upcoming data.
`impact`	No	high (default) or all.
`country`	No	Two-letter country code, e.g. US, GB, EU, JP.
`end_utc`	No	Exclusive end timestamp with timezone. Overrides the relative look-back window.
`start_utc`	No	Inclusive start timestamp with timezone, e.g. 2026-10-14T00:00:00-04:00.
`days_ahead`	No	Upcoming window in days (0-14, default 3; 0 skips it).

Output Schema

Name	Required	Description	Default
`error`	No
`released`	Yes
`upcoming`	Yes
`as_of_utc`	No
`data_note`	No
`days_ahead`	No
`data_status`	No
`query_window`	No
`withheld_rows`	No
`returned_counts`	No
`archive_coverage`	No
`newest_result_utc`	No
`release_data_status`	No
`released_window_hours`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 19, 2026

addedInput schema / properties / end_utc

Added value: +{
+  "description": "Exclusive end timestamp with timezone. Overrides the relative look-back window.",
+  "type": "string"
+}

changedInput schema / properties / hours / description

Previous value: -"Released-data look-back in hours (1-336, default 48)."New value: +"Look back 1-1440 hours; default 48. Actual coverage is disclosed in archive_coverage."

addedInput schema / properties / query

Added value: +{
+  "description": "Up to eight title words, e.g. CPI, payrolls, or retail sales. Filters both released and upcoming data.",
+  "type": "string"
+}

addedInput schema / properties / start_utc

Added value: +{
+  "description": "Inclusive start timestamp with timezone, e.g. 2026-10-14T00:00:00-04:00.",
+  "type": "string"
+}

addedOutput schema / properties / archive_coverage
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / query_window
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / withheld_rows
```
Added value: +{
+  "type": "object"
+}
```

Changed10 schema fields changedOct 18, 2026
- addedOutput schema / properties / as_of_utc
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data_note
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data_status
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / newest_result_utc
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / release_data_status
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / released / items / properties / price_data_status
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / released / items / properties / surprise / description
```
Added value: +"Numerical comparison: above_forecast, below_forecast, in_line, or unavailable. Not market direction."
```
- addedOutput schema / properties / released / items / properties / url
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / returned_counts
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / properties / upcoming / items / properties / url
```
Added value: +{
+  "type": "string"
+}
```
AddedOct 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower. The description earns credit by disclosing the content shape (actual/forecast/previous, surprise direction, measured reaction in the minutes after release) and that results default to high-impact releases, with archive coverage disclosed via a parameter — substantive behavioral context beyond the annotations.

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?

Two sentences, front-loaded with what the tool returns before the use cases. The parenthetical field list is dense but each element is informative; no filler sentences.

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?

An output schema exists so return values need not be described, and annotations carry safety. The description covers the released-data plus forward-calendar duality and the high-impact default, leaving only minor gaps such as pagination/limits behavior, which the schema handles.

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 description coverage is 100%, so the schema already documents all eight parameters including the 'high' default for impact. The description's 'defaults to high-impact releases' largely restates the schema default, adding no syntax or format detail the agent doesn't already have; baseline 3 applies.

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?

States a specific resource (released economic data: CPI, payrolls, PMIs, central-bank decisions) and the exact payload (actual vs forecast vs previous, surprise direction, market reaction), plus the upcoming calendar. This is clearly distinguishable from siblings like earnings or event_screen without opening any schema.

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?

Gives two concrete usage exemplars ('what did CPI come in at and how did markets react', 'what data is out this week') that map to the released-data and calendar halves of the tool. It provides clear context for when to reach for it, but names no alternative sibling or exclusion condition.

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

All MoveSurge 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?