tradingview-finance MCP Server

by henrikxyz

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_economic_calendar

Retrieve global macro economic calendar events from TradingView with filters for date range, country, and importance.

Instructions

Get global macro economic calendar events from TradingView.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_economic_calendar"
  }
}

Input Schema

Name	Required	Description
`from_date`	No	Start date YYYY-MM-DD (defaults to 1 day ago).
`to_date`	No	End date YYYY-MM-DD (defaults to 7 days from today).
`countries`	No	Optional country code filters, e.g. ["US", "DE"].
`importance`	No	Optional importance filters: -1 (low), 0 (medium), 1 (high).

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral traits. The single sentence does not disclose any behavior like data freshness, pagination, rate limits, or authentication needs, leaving significant gaps for the agent.

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 a single, clear sentence with no unnecessary words. It is front-loaded and efficiently communicates the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite an output schema (not shown), the description lacks context about the nature of events (e.g., GDP, CPI), default behavior when parameters are omitted, or how results are structured. This incompleteness would hinder an agent from fully understanding the tool's output and proper use.

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% and each parameter has a clear description (format, defaults, examples) in the schema. The tool description adds no additional parameter context, so the baseline score of 3 is appropriate given the schema already provides sufficient semantics.

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 retrieves economic calendar events from TradingView, specifying the resource ('global macro economic calendar events') and data source. It is sufficiently precise to distinguish from sibling tools like 'get_earnings_calendar' or 'get_dividends_calendar'.

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

Usage Guidelines3/5

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

The description implies usage for macroeconomic events but does not explicitly state when to use this tool over alternatives or provide context such as typical use cases or prerequisites. Guidance is minimal, though the name provides some clarity.

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