Gate Info MCP

info_macro_get_macro_indicator

Read-onlyIdempotent

Official macro stats: latest or series by country/indicator (CPI, rates, jobs). No event feed. Calendar→get_economic_calendar. Dashboard→get_macro_summary. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No	latest (default, snapshot) or timeseries.
`size`	No	Rows; default 20, max 400.
`country`	No	Country display name e.g. United States; wins over country_code if both set.
`end_date`	No	Same as end_time.
`end_time`	No	Range end; alias end_date.
`indicator`	Yes	Exact keyword match on indicator.keyword OR indicator_id.keyword OR slugname.keyword; ASCII case-insensitive via exact variants (original, lower, upper).
`start_date`	No	Same as start_time.
`start_time`	No	Range start; alias start_date; filters date/part_date.
`country_code`	No	ISO code e.g. US when index lacks display name.

Output Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes
`note`	No	Optional empty-result or fallback hint.
`size`	No
`count`	Yes
`total`	Yes
`latest`	No
`country`	No
`end_date`	No
`end_time`	No
`indicator`	Yes
`start_date`	No
`start_time`	No
`timeseries`	No
`duration_ms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds useful context: 'Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.' This goes beyond the annotations and clarifies side effects and limitations.

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 compact and information-dense, using three short sentences. It avoids redundancy and each sentence adds relevant context: what the tool does, alternatives, and safety/public-data characteristics.

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 the tool has 9 parameters (only 1 required) and an output schema, the description provides enough usage boundaries and alternative routes. It mentions the two modes, the main query dimensions (country/indicator), and exclusions. It does not exhaustively explain every parameter, but the schema already covers those 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 description coverage is 100% with detailed per-parameter explanations (e.g., indicator matching, aliases, country_code fallback). The tool description only adds broad context like 'country/indicator' and 'latest or series', so it does not significantly improve parameter understanding beyond the schema.

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?

Description states 'Official macro stats: latest or series by country/indicator' with concrete examples (CPI, rates, jobs), and explicitly differentiates from sibling tools by saying 'No event feed. Calendar→get_economic_calendar. Dashboard→get_macro_summary.' This makes the tool's purpose and scope clear.

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 provides when to use this tool versus alternatives: 'No event feed. Calendar→get_economic_calendar. Dashboard→get_macro_summary.' It also clarifies the two main modes ('latest or series') and gives example indicators, so an agent can decide correctly.

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.