get_macro_contextLive macro snapshot: DXY, US10Y yield, S&P 500, gold, VIX (Yahoo Finance free) + BTC dominance, ETH/BTC, total crypto market cap (CoinGecko free). Plus a coarse RISK_ON / RISK_OFF / MIXED regime.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value beyond annotations by specifying the exact data sources (Yahoo Finance, CoinGecko), the list of assets, and the regime classification. It does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with 'Live macro snapshot', no wasted words. Every sentence adds value: the first enumerates data, the second adds the regime classification.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description could mention how the regime is represented or if the data comes as separate fields. However, for a simple snapshot tool, the current description is nearly complete for an agent to understand the tool's purpose and output. It lacks only a hint about return format.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and schema description coverage is 100% (none needed). The description enriches the tool by listing the constituent data points and regime output, effectively acting as its own parameter documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies: 'Live macro snapshot: DXY, US10Y yield, S&P 500, gold, VIX (Yahoo Finance free) + BTC dominance, ETH/BTC, total crypto market cap (CoinGecko free). Plus a coarse RISK_ON / RISK_OFF / MIXED regime.' This is a specific verb+resource combination that distinguishes it from siblings like get_basic_macro and get_market_context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for macro context but provides no explicit guidance on when to use this tool vs alternatives (e.g., get_basic_macro, get_market_context). It is self-contained but lacks differentiation instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools are specialized, but several pairs have fuzzy boundaries: e.g., get_funding_rates vs get_top_funding_rates, get_basic_macro vs get_macro_context, get_simple_iv vs get_options_iv. An agent could easily select the wrong one.
Most tools follow a 'get_X' pattern with descriptive noun phrases. There are a few exceptions like 'create_api_key' and 'search_markets', but overall the convention is consistent and readable.
With 47 tools, the server is overloaded. While the domain is broad, this many tools makes discovery and selection difficult for an agent, reducing coherence.
The tool set covers an impressively wide range: macro data, funding, prediction markets, OI history, whale tracking, risk analytics, position sizing, backtesting, and signal generation. It leaves no obvious gaps for a crypto trading assistant.