Gate Info MCP

info_macro_get_economic_calendar

Read-onlyIdempotent

Filtered release calendar in a date window. Zero-arg dashboard→get_macro_summary. 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
`size`	No	Rows; default 20, max 400.
`end_date`	No	End YYYY-MM-DD inclusive; default start+30d; sorted by event_date desc.
`event_type`	No	FOMC\|NFP\|CPI\|PPI\|GDP\|PCE\|...; empty or all = no filter.
`importance`	No	Importance filter; ignored if index lacks field.
`start_date`	No	Start YYYY-MM-DD for event_date; default today UTC; if only end_date set, start defaults today.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`size`	No
`count`	Yes
`items`	Yes
`total`	Yes
`end_date`	No
`event_type`	No
`importance`	No
`start_date`	No
`duration_ms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.5/5.0

Behavior5/5

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

The annotations already indicate readOnly, idempotent, openWorld, and non-destructive behavior, and the description adds further transparency by stating there is no account access, order placement, or fund transfer involvement. It also includes a 'not investment advice' disclaimer, which goes beyond the annotations in clarifying the tool's limitations. No contradictions exist between the description and 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 composed of four short sentences, each serving a distinct purpose: core function, sibling alternatives, data nature, and risk disclaimer. There is no redundant wording or unnecessary detail, making it both concise and well structured.

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 that an output schema is present and the input schema fully describes all optional parameters, the description provides enough context for an agent to select and call the tool correctly. It covers alternative tool selection, read-only behavior, and relevant disclaimers without needing to enumerate return fields or parameter details.

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 descriptions already cover all five parameters at 100% coverage, including defaults, date formats, and filter semantics, so the tool description does not need to repeat them. The description only adds a general reference to a 'date window' and optional invocation, but the parameter meanings are fully conveyed by the schema. This is the appropriate baseline score given the high schema coverage.

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

Purpose4/5

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

The description states that the tool provides a filtered release calendar in a date window, clearly identifying the resource and scope. It lacks an explicit verb such as 'returns' or 'lists,' though the tool name and context make the action unambiguous. It also distinguishes itself from sibling tools by pointing to get_macro_summary and get_macro_indicator for related use cases.

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?

The description explicitly tells the agent when to use alternatives: zero-arg dashboards should go to get_macro_summary, and indicator snapshots or series should go to get_macro_indicator. It also notes that the data is read-only public research, reinforcing appropriate usage boundaries. This leaves no ambiguity about when this tool should be selected.

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.