Skip to main content
Glama
Sign In

Stocklake — AI Stock Intelligence

by dev.stocklake.api
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 1 (default 1), lookback_days max 2, limit max 20. Pro: days max 14 (default 3), 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 1 for guest and free, 3 for Pro. Max 1 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. Changed4 schema fields changed
    • addedInput schema / properties / days / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / days / default
      Previous value: -3New value: +null
    • changedInput schema / properties / days / description
      Previous value: -"Look-ahead window in days for upcoming events (default 3). Max 7 for guest and free, 14 for Pro."New value: +"Look-ahead window in days for upcoming events. Default 1 for guest and free, 3 for Pro. Max 1 for guest and free, 14 for Pro."
    • removedInput schema / properties / days / type
      Removed value: -"integer"
  2. 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."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only, idempotent, non-destructive annotations, the description discloses important behavior: released items always carry a real actual value, diff is arithmetic rather than a beat/miss judgment, upcoming items never carry actual, and limit truncation preserves major-economy prints. It also explains guest/free versus Pro caps and the capping response with pro_unlocks.

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 front-loaded and organized around the two buckets, flags, and tier limits. Some tier and parameter details repeat the schema, but most of the length carries non-obvious semantic distinctions that matter for correct use.

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 the tool's complexity, five optional parameters, rich annotations, and an output schema, the description is complete enough to call it correctly. It covers bucket semantics, actual/diff meaning, key_event interpretation, sorting/truncation behavior, and tier-based capping.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds useful meaning beyond the schema, especially that limit applies independently per bucket and that truncation should not drop major-economy releases, and it reinforces the lag rationale for lookback_days and the event-type meaning of key_events_only.

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 and scope: upcoming and recently released macro/economic events such as rate decisions, CPI, GDP, PMI, and payrolls. It clearly distinguishes this from company-level siblings like get_earnings_calendar by framing the tool as macro/economic events, and it explains the two returned buckets.

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 gives clear usage context by defining the released_recent and upcoming buckets, and it explains when to use filters such as key_events_only=true and major_only=true. It does not explicitly name alternative sibling tools or state when not to use this one, so it stops short of a 5.

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