Skip to main content
Glama

terminalfeed

by io.github.RipperMercs

tf_premium_macro

Premium composed macroeconomic snapshot in one HTTP call. Includes FRED economic series (Fed rate, CPI, unemployment, GDP growth, 10-year treasury), 4 USD-base forex pairs (EUR, JPY, GBP, CHF) via Frankfurter, and oil/natural gas via FRED. All sources are public/gov (FRED, US government, public domain) or ECB reference rates (Frankfurter). Costs 2 credits ($0.04 USDC). Requires Authorization: Bearer tf_live_<64-char-hex>. Optional ?history=30d adds 30-day historical series. Note: US equity indices (SPY/DIA/QQQ), VIX, and gold were removed 2026-07-23 (Finnhub/Kraken are not licensed for commercial redistribution).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
historyNoWhen set to 30d, FRED entries include a series array of 30 daily observations and forex.series is populated.

TDQS

A4.5/5.0
Behavior5/5

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

The description goes beyond annotations by disclosing cost (2 credits), authentication requirement, source licensing, and a changelog note about removed indices. This adds valuable behavioral context without contradicting the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false).

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

Conciseness5/5

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

The description is a single, well-structured paragraph that front-loads the main purpose and then concisely covers contents, sources, cost, auth, optional parameter, and a removal note. Every sentence provides useful information with no redundancy or fluff.

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?

Despite having no output schema, the description gives a thorough overview of what the tool returns (FRED series, forex pairs, oil/gas), the historical option, and important caveats. It is sufficiently complete for an agent to decide when and how to invoke the tool.

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?

The single optional parameter is fully documented in the input schema (100% coverage). The description briefly repeats the history=30d behavior but adds no new details beyond what the schema already states, so it does not significantly compensate or enhance parameter understanding.

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 states the tool's action: 'Premium composed macroeconomic snapshot in one HTTP call.' It lists the specific contents (FRED series, forex pairs, oil/gas) and distinguishes itself from siblings by being a composed macro snapshot rather than a single-asset or economic data point tool.

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 description provides clear context for when to use the tool: for a one-call macro snapshot with cost, auth, and optional history details. However, it does not explicitly mention alternatives or exclusions, lacking direct comparison to siblings like tf_economic_data or tf_forex.

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

All terminalfeed toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (e.g., tf_btc_price vs tf_fear_greed), but there is some overlap between free and premium aggregated tools (e.g., tf_briefing, tf_premium_briefing, tf_premium_agent_context). However, descriptions explicitly differentiate them by content and cost.

Naming Consistency5/5

All tools follow a consistent pattern: 'tf_' prefix (with 'tf_premium_' for premium ones) and snake_case. Names are descriptive and predictable, e.g., tf_btc_price, tf_earthquakes, tf_premium_macro.

Tool Count3/5

27 tools is on the high side, but the server covers a broad domain (crypto, finance, earthquakes, AI trends, payment system, etc.). Each tool serves a specific purpose, so the count is borderline acceptable but feels slightly heavy.

Completeness4/5

The tool surface covers a wide range of data feeds: crypto, forex, macro indicators, earthquakes, HN, HuggingFace, prediction markets, payment system, and service status. Minor gaps exist (e.g., no dedicated stock prices tool beyond premium macro, no weather), but overall it's comprehensive for a terminal feed.

Resources