Skip to main content
Glama
Sign In

horizon-pulse

by io.github.horizon-pulse
OverviewDiscussionsAdmin

Money Market Reference Rates

money_market_rates
Read-onlyIdempotent

No charge (no x402, no payment); reference feed, not a paid service. Published NY Fed reference rates as released; market data only, not a forecast, not a recommendation. SOFR, EFFR, OBFR, TGCR and BGCR as published, with each rate's NY Fed source URL, terms notices and a holiday-aware status (fresh, PENDING, STALE, no publish, UNVERIFIED holiday status). Params: rates (comma list), last (1-10) or startDate+endDate (YYYY-MM-DD, <=31 days, >=2018-04-02). Horizon Pulse is not affiliated with the New York Fed. The New York Fed does not sanction, endorse, or recommend any products or services offered by Horizon Pulse. Horizon Pulse is also not affiliated with the Federal Reserve System. Data are passed through unchanged from the NY Fed Markets Data API under the New York Fed Terms of Use and may not be current; the same values are free at markets.newyorkfed.org.

Input Schema

NameRequiredDescriptionDefault
lastNoLast n observations per rate, 1-10 (exclusive with startDate/endDate)
ratesNoComma list from SOFR,EFFR,OBFR,TGCR,BGCR (default all five)
endDateNoYYYY-MM-DD, >= startDate
startDateNoYYYY-MM-DD, >= 2018-04-02; needs endDate; span <= 31 days

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The description provides massive behavioral context beyond annotations, detailing data status (fresh, PENDING, STALE), specific sourcing (NY Fed Markets Data API), and legal disclaimers that define how the data should be used.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is excessively long, dominated by repetitive legal disclaimers and affiliation notices which are necessary for the domain but poor for conciseness in a tool definition.

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 regulated financial reference tool, the definition is incredibly thorough, covering data provenance, format, limitations, and necessary legal warnings. Nothing crucial is missing.

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?

Although schema coverage is 100%, the description adds necessary semantic context by enumerating the acceptable rate types (SOFR, EFFR, etc.) and clarifying mutual exclusivity between the 'last' and date-range parameters.

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 identifies the tool's purpose: retrieving published NY Fed reference rates like SOFR, EFFR, etc. It specifies the data source and the specific types of financial markers it handles.

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?

The tool provides critical usage boundaries by stating it is a reference feed, not a forecast or paid service. It clearly sets expectations regarding data currency and recommendation status.

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

All horizon-pulse toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources