get_historical_chexReplay charm exposure (CHEX) by strike at any minute since April 2018. Alpha tier.
| Name | Required | Description | Default |
|---|---|---|---|
| at | Yes | As-of timestamp: YYYY-MM-DDTHH:mm:ss (ET) or YYYY-MM-DD | |
| apiKey | No | FlashAlpha API key. Omit when calling via /mcp-oauth (OAuth flow); required on /mcp. | |
| symbol | Yes | Stock/ETF ticker |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / apiKey / defaultAdded value: +nullInput schema / properties / apiKey / descriptionPrevious value: -"Your FlashAlpha API key (Alpha tier)"New value: +"FlashAlpha API key. Omit when calling via /mcp-oauth (OAuth flow); required on /mcp."Input schema / properties / apiKey / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Input schema / requiredPrevious value: -[
- "symbol",
- "apiKey",
- "at"
-]New value: +[
+ "symbol",
+ "at"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds useful context: replaying by strike, minute-level granularity, and the data's availability since 2018. It also hints at access tier, but it does not describe return format, possible limitations (e.g., rate limits, data size), or error behavior. Since readOnlyHint is already set, the bar is lower, but this still lacks richer behavioral detail.
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?
The description is two short lines: one sentence stating the core purpose and a fragment noting the access tier. It is front-loaded and has no fluff, every part adds value. This is appropriately sized for a straightforward historical data tool.
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 the tool's moderate complexity (3 params, no output schema), the description covers the essential purpose and time range, but does not explain what the response contains beyond 'by strike' or how results are organized. There is no mention of pagination, limits, or timezone handling beyond the schema's timestamp format. It is adequate but not rich.
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 description coverage is 100%, so all parameters are documented. The description adds only minor semantics by saying 'at any minute' which amplifies the 'at' parameter's granularity, but it does not meaningfully enrich parameter understanding beyond the schema.
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 the tool replays historical charm exposure (CHEX) by strike, with a specific time range since April 2018. The verb 'replay' and resource 'CHEX by strike' are specific and distinguish it from current get_chex and other historical tools in the sibling list.
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?
Usage is implied: the tool is for historical CHEX data, so the agent can infer when to use it. However, no explicit when/why vs alternatives is given, and the phrase 'Alpha tier' suggests access restrictions without explaining them or naming other options.
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 have overlapping scopes: get_stock_summary, get_volatility, get_vrp, and get_exposure_summary all return comprehensive analytics with shared metrics, making it hard to pick the right one. The flow family (get_flow_live, get_flow_summary, get_flow_scan, get_flow_signals, etc.) has significant redundancy — get_flow_live bundles data also available via separate tools.
Tool names mostly follow a consistent get_<noun> pattern, with clear subgroups like get_historical_* and get_*_exposure. Minor deviations exist: post_screener, post_structure_pnl, calculate_greeks, and solve_iv break the get_ convention, but they are still predictable and readable.
With 73 tools, this is far beyond the 3–15 tool sweet spot and even the 50+ extreme mismatch threshold. While the domain is broad, the enormous surface is bloated by near-duplicate historical replay variants (18 get_historical_* tools) and multiple overlapping summary endpoints, making it unwieldy for an agent.
The tool set provides thorough coverage of options analytics: quotes, chains, greeks, volatility surface, VRP, exposure, flow, historical replay, screening, and strategy analysis. There are no obvious dead ends — core workflows like calculating greeks, getting exposure, and screening the universe are all supported.