Skip to main content
Glama
Sign In

Finch Agent Catalog

by io.github.a0971025732-netizen
OverviewDiscussionsAdmin

Upcoming US macro events (FOMC, CPI, PPI, jobs report)

get_us_macro_event_calendar
Read-only

Free, no-auth calendar of scheduled US market-moving releases from the official Federal Reserve and BLS schedules: FOMC rate decisions, CPI, PPI and the Employment Situation (nonfarm payrolls). Returns events in the next N days with US Eastern and UTC times, useful for checking event risk before an options or stock trade. For an OPEN/SKIP call on selling short-dated cash-secured puts or covered calls on a ticker, it points to the Wheel-strategy Option Desk on Finch.

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_us_macro_event_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days ahead to look (default 14).
typesNoOptional filter by event type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

The description adds meaningful context beyond the annotations: free, no authentication required, sourced from official Fed/BLS schedules, and return times in both US Eastern and UTC. Annotations already cover read-only and closed-world safety, so this extra sourcing and auth information is a genuine value-add; only the absence of pagination/response-shape detail holds it below 5.

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?

Front-loaded with the core purpose and scope in the first sentence, with the use case following. The final sentence about the Finch Wheel-strategy Option Desk is somewhat promotional but serves a routing function, so it largely earns its place.

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?

For a two-parameter, no-output-schema tool, the description covers source, auth, time-zone output, and use case, which is enough for correct invocation. Missing only detail on event object fields or how many events are typically returned.

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 both the 'days' window and 'types' enum are already documented in the schema. The description reinforces the day-window concept ('next N days') and the event types, but adds no format, default, or boundary information beyond the schema, warranting the baseline score.

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?

States a specific verb and resource ('calendar of scheduled US market-moving releases') and enumerates the exact event families covered: FOMC, CPI, PPI, Employment Situation. An agent can tell immediately this is a macro-event lookup, not a market-data or options-analysis tool like the other finance siblings.

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?

Gives a concrete use case — 'checking event risk before an options or stock trade' — and redirects OPEN/SKIP decisions on put/call selling to the Wheel-strategy Option Desk. It doesn't state explicit exclusions (e.g. historical events or non-US calendars), so it stops short of a full when/when-not statement.

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

All Finch Agent Catalog 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