SiteCheck Crypto & Finance

Investing.com economic calendar for a date range: each

dev_investing_com_economic_calendar

Read-only

Investing.com economic calendar for a date range (up to 7 days): each release with UTC time, country, currency, event name, category, importance (low/medium/high), reference period, actual, forecast and previous values with unit, Investing's actual-vs-forecast verdict, preliminary flag and the publishing source. Filter by country code, currency or minimum importance. Read from the API the Investing.com calendar page calls. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "dev_investing_com_economic_calendar"
  }
}

Input Schema

Name	Required	Description
`to`	No	Last day, YYYY-MM-DD, at most 7 days after from (default = from)
`from`	No	First day, YYYY-MM-DD (default today, UTC)
`limit`	No	Releases, 1 to 500 (default 200)
`country`	No	Two-letter country code, e.g. US, GB, DE, TR
`currency`	No	Currency code, e.g. USD, EUR
`minImportance`	No	low (default), medium or high

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint it discloses the upstream source (the API behind the Investing.com calendar page) and an explicit pricing model: $0.002 USDC per successful call via x402 across Base/Solana/Arc, with failed calls uncharged. That payment detail is materially useful before calling, though return shape and truncation behavior are left to the output schema.

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?

It is a single dense paragraph that front-loads scope and the date-range limit before filters and pricing. The field enumeration is somewhat long given an output schema exists, but every clause carries information and none is filler.

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?

With 6 optional parameters, full schema coverage, annotations and an output schema, the description covers the gaps that matter: default behavior, the 7-day cap, filtering axes and cost. Nothing essential for a correct call is missing.

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 every parameter is already documented in the input schema, including the 7-day window and the low/medium/high importance levels. The description only restates the filter dimensions and the range cap, adding no syntax or edge-case detail beyond the schema, which matches the baseline 3.

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 names a specific verb and resource ('retrieve Investing.com economic calendar for a date range') and enumerates the exact fields returned, so an agent can tell instantly what it produces. No sibling tool covers economic releases, so the scope is unambiguous without sibling comparison.

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?

It states a clear operating context: date range capped at 7 days, plus filtering by country, currency or minimum importance. It does not name alternatives or say when not to use it, but for this catalog no close substitute exists, so the implied guidance is strong.

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

All SiteCheck Crypto & Finance 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?