Skip to main content
Glama

Stocklake — AI Stock Intelligence

by dev.stocklake
OverviewDiscussionsAdmin

Get Economic Calendar

get_economic_calendar
Read-onlyIdempotent

Upcoming and recently-released macro/economic events -- interest rate decisions, CPI, GDP, PMI, unemployment, payrolls, retail sales, and more.

Two buckets:

  • released_recent: events with a real reported value, within the last lookback_days days. Every item here carries a real actual value (never blank) plus diff (actual minus previous -- a plain arithmetic difference, never a beat/miss or consensus judgment; point-in-time consensus is not available).

  • upcoming: not-yet-released events within days. No item here ever carries an actual value.

Every item in both buckets carries key_event: true for the handful of event types that reliably move markets on their own (rate decisions, CPI, GDP, headline Non-Farm Payrolls) -- an event-TYPE flag only, never a beat/miss or directional judgment on the number itself. Set key_events_only=true to filter to just these, or major_only=true to restrict to the 8 largest economies.

Both buckets sort major-economy-first, then by recency -- truncating to limit should never lose a US/EU/UK/JP/CN/DE/FR/CA print to an older or thinner-economy one.

All tiers. Guest and free: days max 7, lookback_days max 2, limit max 20. Pro: days max 14, lookback_days max 7, limit max 50. When a guest/free value is above its cap, the response is served at the cap and carries capped ({param: {requested, served}}) plus a pro_unlocks note. For informational purposes only. Not financial advice.

Input Schema

NameRequiredDescriptionDefault
daysNoLook-ahead window in days for upcoming events (default 3). Max 7 for guest and free, 14 for Pro.
limitNoMax results per bucket, released_recent and upcoming each capped independently (default 20). Max 20 for guest and free, 50 for Pro.
major_onlyNoRestrict to the 8 largest economies (United States, Euro Area, United Kingdom, Japan, China, Germany, France, Canada). Default false returns all countries.
lookback_daysNoLook-back window in days for recently-released events (default 2). Max 2 for guest and free, 7 for Pro. Actual values arrive with about a 1-day reporting lag, so a same-day-only window misses real releases -- keep this at 2+ to reliably see them.
key_events_onlyNoRestrict to the small subset of event types that reliably move markets on their own: interest rate/rate decisions, CPI, GDP, and headline Non-Farm Payrolls. Default false returns every event matching the broader base filter (also includes PMI, unemployment, other payrolls components, retail sales, ADP, inflation).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"Look-ahead window in days for upcoming events (default 3, max 14)."New value: +"Look-ahead window in days for upcoming events (default 3). Max 7 for guest and free, 14 for Pro."
    • changedInput schema / properties / limit / description
      Previous value: -"Max results per bucket, released_recent and upcoming each capped independently (default 20, max 50)."New value: +"Max results per bucket, released_recent and upcoming each capped independently (default 20). Max 20 for guest and free, 50 for Pro."
    • changedInput schema / properties / lookback_days / description
      Previous value: -"Look-back window in days for recently-released events (default 2, max 7). Yahoo's own actual value has a confirmed ~1-day reporting lag, so a same-day-only window misses real releases -- keep this at 2+ to reliably see them."New value: +"Look-back window in days for recently-released events (default 2). Max 2 for guest and free, 7 for Pro. Actual values arrive with about a 1-day reporting lag, so a same-day-only window misses real releases -- keep this at 2+ to reliably see them."
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Despite already-rich annotations (readOnly, idempotent, non-destructive), the description adds substantial behavioral detail: the released_recent vs upcoming split, the guarantee that upcoming items never carry actual values, the meaning of diff, the key_event flag, major-economy-first sorting, and tier-cap/capped-response behavior.

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?

The description is long but well-structured and front-loaded, with bullets separating bucket semantics, filtering flags, sorting, and tier limits. Most sentences earn their place, though some schema-level details are repeated.

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 read-only calendar tool with five optional parameters and an output schema, the description covers the key behavioral and filtering nuances an agent needs. It explains the returned buckets and flags even though the output schema exists.

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 the input schema already documents each parameter thoroughly. The description reinforces defaults and caps but adds little parameter-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific resource (upcoming and recently-released macro/economic events) and enumerates concrete event types, clearly distinguishing this calendar from earnings or corporate-event siblings.

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?

It defines the two buckets and filter behavior, which implies when to use the tool, but it never names an alternative tool or explicitly says when not to use this one. Routing to siblings such as get_earnings_calendar is left to inference.

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

All Stocklake — AI Stock Intelligence toolsInspect
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