Skip to main content
Glama

get_macro_market_signal

Read-only

Use when a current macro environment snapshot is needed for a trading brief, CFO board presentation, or investment committee context. Returns Fed funds rate, Treasury yields, CPI, PCE, and employment data when FRED API is configured. Example: Fed funds 5.33%, 10Y 4.42%, CPI 3.1% — rates and inflation above long-run targets, labor market tight — LATE-CYCLE positioning signal. Source: FRED St. Louis Fed, daily update. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
signal_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses a real prerequisite (FRED API must be configured), the underlying source (FRED St. Louis Fed), update cadence (daily), and a per-call cost of $0.02 USDC. That cost and dependency information is genuinely additive, though it does not discuss failure modes or staleness when FRED is unavailable.

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 usage condition is front-loaded, followed by return fields, an illustrative example, provenance, and cost. The example with sample figures is slightly verbose but illustrates how the output should be interpreted, so most sentences earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does a reasonable job enumerating return fields and giving a sample reading. However, the sole input parameter is left unexplained, leaving a meaningful gap for an agent deciding how to invoke it correctly.

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

Parameters2/5

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

There is one parameter, signal_type, with 0% schema description coverage, and the description never mentions it. The agent must guess what values signal_type accepts or what it controls, so the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (current macro environment snapshot) and enumerates exactly what it returns: Fed funds rate, Treasury yields, CPI, PCE, and employment data. This is concrete and distinguishable from data-specific siblings, though it does not explicitly contrast itself with get_imf_weo_macro_snapshot or get_macro_playbook.

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 use contexts (trading brief, CFO board presentation, investment committee context), which tells the agent when this tool fits. It stops short of stating when not to use it or naming which sibling to prefer for alternative macro needs, so no explicit routing guidance is present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources