Skip to main content
Glama

FlashAlpha

by com.flashalpha.lab
OverviewDiscussionsAdmin

Get Historical Stock Quote

get_historical_stock_quote
Read-only

Replay a stock bid/ask/mid at any minute since April 2018. Alpha tier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atYesAs-of timestamp: YYYY-MM-DDTHH:mm:ss (ET) or YYYY-MM-DD
apiKeyNoFlashAlpha API key. Omit when calling via /mcp-oauth (OAuth flow); required on /mcp.
symbolYesStock ticker

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / apiKey / default
      Added value: +null
    • changedInput schema / properties / apiKey / description
      Previous value: -"Your FlashAlpha API key (Alpha tier)"New value: +"FlashAlpha API key. Omit when calling via /mcp-oauth (OAuth flow); required on /mcp."
    • changedInput schema / properties / apiKey / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / required
      Previous value: -[
-  "symbol",
-  "apiKey",
-  "at"
-]New value: +[
+  "symbol",
+  "at"
+]
  2. Changed5 schema fields changed
    • changedInput schema / properties / apiKey / description
      Previous value: -"Your FlashAlpha API key"New value: +"Your FlashAlpha API key (Alpha tier)"
    • addedInput schema / properties / at
      Added value: +{
+  "description": "As-of timestamp: YYYY-MM-DDTHH:mm:ss (ET) or YYYY-MM-DD",
+  "type": "string"
+}
    • removedInput schema / properties / date
      Removed value: -{
-  "description": "Date YYYY-MM-DD",
-  "type": "string"
-}
    • removedInput schema / properties / time
      Removed value: -{
-  "default": null,
-  "description": "Optional time HH:mm (e.g. 10:30). Omit for full day.",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • changedInput schema / required
      Previous value: -[
-  "symbol",
-  "apiKey",
-  "date"
-]New value: +[
+  "symbol",
+  "apiKey",
+  "at"
+]
  3. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description's 'Replay' aligns with a read-only operation. The description adds the historical range (since April 2018) and minute-level precision, but doesn't disclose return format, data availability caveats, or the 'Alpha tier' implications. With annotations covering safety, the added context is moderate.

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?

Two short sentences with no waste. Every word contributes to the tool's purpose and scope.

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?

For a simple historical quote tool, the description covers the essential behavior (bid/ask/mid replay) and time range. While there's no output schema and no explicit description of the response shape, the terms 'bid/ask/mid' and 'quote' sufficiently convey the expected return. The 'Alpha tier' note adds a slight caveat but isn't fully explained.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully describes all parameters. The description adds no additional parameter-level meaning beyond what's in the schema; 'at any minute' and 'stock' echo the schema. Baseline 3 is appropriate because the schema does the heavy lifting.

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?

The description uses the specific verb 'Replay' with a clear resource: 'stock bid/ask/mid' at a specified minute. It also provides a time boundary (since April 2018) and distinguishes itself from current stock quotes (get_stock_quote) and other historical tools focused on different metrics.

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?

The description clearly implies when to use the tool: to retrieve a historical stock quote at minute granularity. It doesn't explicitly mention alternatives, but the context and sibling names support differentiation. No exclusion or alternative guidance is provided, but the usage scenario is unmistakable.

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

All FlashAlpha toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources