Skip to main content
Glama

AINDEX

Macro and sentiment

macro_context
Read-only

VIX, the dollar index, the US 10-year yield, S&P 500 and Nasdaq 100 futures, gold and oil with their day and week moves; the US releases of medium and high impact in the last 12 hours and next 3 days; crypto fear and greed, the Coinbase premium, BTC and ETH spot ETF flows (TrueNorth, labelled); and Polymarket's odds on the Fed.

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": "macro_context"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description is not obliged to restate safety. It does add genuine behavioral context beyond the annotations: the release window (last 12 hours / next 3 days), the impact filter (medium and high), and provenance notes such as 'TrueNorth, labelled' and Polymarket. It says nothing about freshness, caching, payload size, or how the multiple data families are grouped in the response.

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?

A single dense but well-structured sentence, ordered by data family (tradfi markets, US releases, crypto sentiment, prediction markets) rather than as a random list. Every clause names actual payload content that matters because there is no output schema; nothing is redundant, though the sentence is long and could be split for scanning.

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?

With no output schema, the description carries the full burden of telling the agent what comes back, and it does so item by item, including time windows and source labels. Combined with annotations that cover the read-only, open-world profile, an agent has enough to decide to call it and to know what to expect.

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 the parameter_semantics baseline of 4 applies and there is no parameter meaning to clarify. Nothing in the description misdescribes a calling contract.

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 the exact resource – a macro and sentiment snapshot – and enumerates its contents (VIX, DXY, 10Y yield, index futures, commodities, US releases, crypto sentiment, ETF flows, Fed odds), which operationally distinguishes it from quote, derivatives and news siblings. It lacks an explicit verb (e.g. 'returns a snapshot of'), so the action must be inferred from the noun list, and it never names a sibling it replaces.

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?

There is no explicit when-to-use or when-not-to-use statement, but the enumerated contents strongly imply the use case: call this when you need macro backdrop or market sentiment in one shot. The overlap with a news or release-oriented sibling is left unaddressed, so the agent must infer routing from content alone.

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