Skip to main content
Glama

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds genuinely useful non-schema context: the data source (FRED/EIA), the separation of verifiable FOMC facts from forward-looking model interpretation, and a per-call cost of $0.50 USDC — cost disclosure is materially valuable for agent decision-making.

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 usage trigger, followed by contents, an example, source and price — a sensible priority order. The 11-item indicator list is long but each item is selection-relevant, and no sentence is pure filler.

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?

There is no output schema and no parameters, so the description carries the burden of explaining the return. It lists what is returned and notes facts are separated from interpretation, but says nothing about response shape, units, timestamps, or freshness, which matters for a live market-data 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 input schema has zero parameters and 100% schema coverage, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies.

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 verb+resource ('full live signal stack in one call') and enumerates the exact indicators returned (Fed funds, 2s10s, VIX, BTC, WTI, silver, gold, DXY, SOFR, MOVE), so an agent knows precisely what it gets. It stops short of differentiating itself from the many sibling benchmark/intelligence tools, which is why it isn't a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/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 usage context and implicitly frames this as a bundle alternative to multiple single-indicator calls. However, no explicit when-not conditions or named alternatives are provided, so the guidance remains implied rather than directive.

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