search_batch

Search similar chart patterns across up to 20 stock symbols simultaneously. Retrieve forward return statistics for each symbol on the same date to compare historical outcomes.

Instructions

Search for similar patterns across multiple symbols at once.

Batch version of search_charts — runs parallel searches for up to 20 symbols
on the same date and returns forward return statistics for each.

Args:
    symbols: List of ticker symbols (max 20), e.g. ['AAPL', 'MSFT', 'NVDA']
    date: Date in YYYY-MM-DD format
    timeframe: Session: rth, premarket, rth_3d, rth_5d (default rth)
    top_n: Number of results per symbol (1-50)

Input Schema

TableJSON Schema

Name	Required	Default
`symbols`	Yes
`date`	Yes
`timeframe`	No	rth
`top_n`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Tool Definition Quality

A4.4/5.0

Behavior4/5

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

Discloses parallel execution, returns 'forward return statistics', and specifies the 20-symbol cap, though it omits read-only/idempotency status.

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 purpose statement followed by dense but readable Args section; slightly informal 'Args:' formatting but every sentence provides essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Appropriately mentions return type (forward return statistics) without duplicating output schema details; covers all parameters and key constraints for the tool's complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Comprehensively compensates for 0% schema coverage by documenting all 4 parameters with examples, formats (YYYY-MM-DD), enum values (rth, premarket, etc.), and constraints (1-50, max 20).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Explicitly states it searches for similar patterns across multiple symbols and clearly distinguishes itself as the 'Batch version of search_charts'.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage context by contrasting with search_charts and mentions the 20-symbol limit, but doesn't explicitly state when to prefer the single-symbol alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Chart Library

search_batch

Instructions

Input Schema

Output Schema

Tool Definition Quality

Other Tools

Latest Blog Posts

MCP directory API