Gate Info MCP

info_macro_get_macro_summary

Read-onlyIdempotent

Zero-arg macro dashboard: key snapshots plus upcoming releases. Filtered calendar list→get_economic_calendar. Indicator snapshot or series→get_macro_indicator. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`total`	Yes
`indicators`	Yes
`duration_ms`	Yes
`next_events`	Yes
`snapshot_time`	Yes
`indicators_total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedAug 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedInput schema / properties
```
Removed value: -{}
```
- addedOutput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / indicators / additionalProperties / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / next_events / items / additionalProperties
```
Added value: +true
```
- changedOutput schema / properties / next_events / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
First observedApr 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description adds that it is public research data with no account access, no order placement or fund transfers, and not investment advice, giving extra behavioral context.

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 concise and well-structured, conveying key information in two sentences plus a brief disclaimer without unnecessary verbosity.

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 zero-argument tool, the description fully covers what it returns, how to get more specific data via other tools, and includes a relevant disclaimer, making it contextually complete.

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?

With zero parameters, the schema is trivially complete and the description adds no parameter details, but the baseline for zero-parameter tools 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 is a zero-argument macro dashboard providing key snapshots and upcoming releases, making its purpose specific and distinct from sibling tools.

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

Usage Guidelines5/5

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

It explicitly instructs when to use alternative tools: for filtered calendar lists use get_economic_calendar, and for indicator snapshots/series use get_macro_indicator, providing clear usage guidance.

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

All Gate Info MCP 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.