Skip to main content
Glama

FlashAlpha (Unofficial)

Flashalpha Levels

flashalpha_levels
Read-onlyIdempotent

Get key options-derived levels for an underlying, gamma flip level, call wall, and put wall. These act as magnet / support / resistance levels driven by dealer gamma. Example: flashalpha_levels({ symbol: "SPY", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "SPY",
      "_apiKey": "your-flashalpha-api-key"
    },
    "name": "flashalpha_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesUnderlying ticker symbol, e.g. "SPY", "AAPL"
_apiKeyYesFlashAlpha API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuinely new context by explaining that these levels act as magnet/support/resistance driven by dealer gamma, which is interpretive meaning not present in annotations. It does not mention data freshness or error behavior, so it falls short of a 5.

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?

The content is front-loaded with the purpose and output fields before the interpretation and example. The example call is slightly redundant with the schema examples, but nothing is confusing or bloated.

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

Completeness3/5

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

For a simple two-parameter read tool with full annotations and full schema coverage, the description is adequate: it says what is returned and what the values mean. It lacks any routing guidance against its close siblings, which is the main remaining gap an agent would need.

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 coverage is 100%, so both symbol and _apiKey are already documented in the input schema. The example repeats the schema's example values rather than adding new meaning about formats or constraints, so baseline 3 applies.

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?

The description names a specific resource and enumerates the exact outputs: gamma flip level, call wall, and put wall for an underlying. It is clearly a data-retrieval tool, though it does not distinguish itself from the sibling flashalpha_gex, which plausibly overlaps.

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

Usage Guidelines3/5

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

Usage is only implied by 'for an underlying' and the example call. There is no explicit statement of when to use this versus flashalpha_gex or the other flashalpha tools, and no prerequisites or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.