get_follow_through

Analyze historical outcomes of chart pattern matches by calculating forward returns 1, 3, 5, and 10 days later. Retrieve percentage gains and cumulative paths to validate trading signals.

Instructions

Get forward return analysis for search results.

Pass the results from search_charts to see what happened 1, 3, 5, and 10
days later in each historical match. Returns % returns and cumulative paths.

Args:
    results: Search results from search_charts (list of {symbol, date, timeframe, metadata})

Input Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Tool Definition Quality

A4.3/5.0

Behavior4/5

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

Discloses specific look-ahead periods (1, 3, 5, 10 days) and return formats (% returns, cumulative paths) despite no annotations being provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise with three information-dense sentences; front-loaded with purpose, followed by usage instructions and parameter details.

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?

Sufficiently complete given the presence of an output schema; mentions key behavioral details (time horizons) without redundantly detailing return values.

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?

With 0% schema description coverage, the description crucially compensates by detailing the expected 'results' structure (list of {symbol, date, timeframe, metadata}) and its source.

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?

Clearly states it performs forward return analysis on search results and specifically names 'search_charts' as the prerequisite, distinguishing it from sibling search and analysis tools.

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?

Explicitly instructs to pass results from 'search_charts', establishing a clear workflow sequence, though lacks explicit 'when not to use' guidance.

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