get_market_indices
Get major market indices and macro indicators: S&P 500, NASDAQ, VIX, 10-Year Treasury, WTI Oil, Gold, USD/EUR. Data from FRED (St. Louis Fed).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Get major market indices and macro indicators: S&P 500, NASDAQ, VIX, 10-Year Treasury, WTI Oil, Gold, USD/EUR. Data from FRED (St. Louis Fed).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so description carries burden. Specifies data source (FRED) and a fixed set of indices, implying read-only behavior. Lacks details on update frequency or limitations.
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?
Extremely concise: single sentence plus a list. No wasted words or redundancy.
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?
Lists returned indices but no output schema; could describe return structure (e.g., timestamps, numeric values). Acceptable for a simple retrieval tool.
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?
Zero parameters; baseline 4. No additional parameter info needed since none exist.
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?
Clearly states the tool gets major market indices and macro indicators, listing specific ones (S&P 500, NASDAQ, VIX, etc.). Differentiates from siblings which involve holdings and stock quotes.
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?
Implies use for broad market data; no explicit alternatives but context suggests not for individual stocks or holdings. Could be improved with direct comparisons.
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.
Each tool targets a distinct area: institutional holdings, market indices, and stock quotes, with no overlap in purpose.
All tool names follow a consistent 'get_' prefix followed by a descriptive noun phrase (institutional_holdings, market_indices, stock_quotes).
Three tools is appropriate for a focused market data server, covering key data points without being too sparse or too heavy.
Covers stock quotes, indices, and institutional holdings, but lacks historical data, fundamental metrics, or news, which are common in market data APIs.