Skip to main content
Glama

Stratalize Intelligence

Get Macro Market Signal

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. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint, destructiveHint=false), the description discloses a hard dependency (FRED API must be configured), a per-call cost ($0.02 USDC), the upstream source (FRED St. Louis Fed), and the refresh cadence (daily update). It also characterizes the output shape with a worked example and an interpretation ('LATE-CYCLE positioning signal'), which the annotations cannot convey.

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 when-to-use clause, then the returned fields, then a concrete example, then source/cost — a sensible order with no filler sentences. The example partially restates the field list already enumerated, a small redundancy, but it earns its place by showing interpretation.

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?

With no output schema, the description carries the return-value burden well by listing data fields plus an illustrative output and a positioning interpretation. The notable gap is the unexplained signal_type parameter and the absence of any error/fallback behavior when FRED is not configured.

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?

The single parameter, signal_type, has 0% schema description coverage and is never mentioned in the description — no meaning, allowed values, or default is given. The description compensates richly on outputs but leaves the one input entirely opaque, so the agent must guess what to pass.

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 (macro environment snapshot) and enumerates the concrete data returned: Fed funds rate, Treasury yields, CPI, PCE, and employment. It implicitly separates itself from the many sibling 'signal' tools by scoping to macro/rates/inflation/labor, though it never names an alternative explicitly.

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 situational triggers — trading brief, CFO board presentation, investment committee context — which tell the agent when this tool is the right pick. It stops short of exclusions or naming when a sibling (e.g. get_imf_weo_macro_snapshot or get_labor_market_benchmark) would be better.

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