Skip to main content
Glama

Stratalize Intelligence

Get Trader Signals

get_trader_signals
Read-only

Use when a macro agent needs a full live signal stack in one call. Returns Fed funds, 2s10s, VIX, BTC, WTI, silver, gold, DXY, SOFR, MOVE, verifiable FOMC facts, model interpretation, and cross-asset sentiment. Example: live rates, vol, and commodities with FOMC facts separated from forward-looking interpretation. Source: FRED/EIA. $0.50 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_trader_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds genuinely non-structured context: data provenance (FRED/EIA), a per-call cost of $0.50 USDC, and the separation of verifiable FOMC facts from forward-looking model interpretation. Freshness/latency and response shape are not disclosed.

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 the return inventory, provenance, and price, which is a sensible ordering. The "Example: live rates, vol, and commodities" sentence largely restates the enumerated series, making it the weakest of the five sentences, though it does clarify the facts-vs-interpretation split.

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 input parameters and no output schema, the description carries the burden of telling the agent what comes back — and it does, listing the series groups, the interpretive layer, and the source. It omits update cadence, delivery format, and error/cost-failure behavior, which are minor for a fixed-feed read tool.

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?

The tool takes zero parameters, so there is no parameter surface for the description to explain and the baseline of 4 applies. Nothing is mismatched or undocumented.

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 uses a specific verb ("Returns") and enumerates the exact signal set delivered: Fed funds, 2s10s, VIX, BTC, WTI, silver, gold, DXY, SOFR, MOVE, plus FOMC facts and sentiment. The "full live signal stack in one call" framing distinguishes it from single-metric siblings such as get_commodity_benchmark, but no sibling is named for contrast.

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?

"Use when a macro agent needs a full live signal stack in one call" gives a clear selection context and implicitly routes single-metric needs elsewhere. It stops short of explicit when-not-to-use exclusions or named alternatives, so it sits just below the top band.

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