Multi-day intraday bars for one ticker (interval 3-240 min, default 3m). Every bar carries absolute open/high/low/close plus fractional change from that day's own open — percentages reset daily, not cumulative. $0.01/day, no day limit.
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | End date YYYY-MM-DD | |
| start | Yes | Start date YYYY-MM-DD | |
| ticker | Yes | Stock ticker (e.g. AAPL) | |
| interval | No | Bar interval in minutes: 3, 6, 9, 12, 15, 30, 60, or 240 (default 3) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description adds value by disclosing that bars carry absolute OHLC plus fractional change from that day's open (reset daily), and pricing is $0.01/day with no day limit. It does not cover read-only nature explicitly but implies it.
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, no redundancy, front-loaded with core purpose and key constraints. Every sentence earns its place.
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?
Although no output schema is provided, the description adequately explains return values (bars with OHLC and fractional change) and pricing limits. Could mention rate limits or pagination, but for a simple query tool it is fairly complete.
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?
Schema coverage is 100% with good parameter descriptions. The description adds context about interval range (3-240 min) and default value (3m), but does not significantly enhance understanding beyond what the schema already provides.
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 states it provides multi-day intraday bars for one ticker with a specified interval range (3-240 min, default 3m). It distinguishes from siblings by specifying 'multi-day' and the unique data fields (fractional change from day's open).
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 historical intraday data over multiple days (no day limit) but does not explicitly contrast with sibling tools like get_bars, query_daily, or query_minute_bars. No when-to-use or alternatives guidance.
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.
Most tools have distinct purposes, but there is some overlap among bar-related tools (get_bars, query_minute_bars, query_range, query_daily). Descriptions are detailed enough to differentiate, but an agent might need to carefully choose the right bar tool.
Naming follows a consistent verb_noun pattern (get_*, query_*, scan_*). The only minor deviation is list_tickers instead of get_tickers, but it's still predictable.
15 tools is well-scoped for a market data API covering prices, fundamentals, filings, insiders, and screening. Each tool serves a clear purpose without being excessive.
The tool set covers a comprehensive range of market data needs: intraday/daily bars, fundamentals, SEC filings, insider transactions, company profiles, and screening. Notable missing features like options data are beyond the stated scope.