Skip to main content
Glama

FlashAlpha (Unofficial)

Flashalpha Greeks

flashalpha_greeks
Read-onlyIdempotent

Black-Scholes (BSM) option greeks calculator, pass spot, strike, days-to-expiry, volatility and option type to get delta, gamma, theta, vega (and higher-order greeks where returned). Example: flashalpha_greeks({ spot: 100, strike: 105, dte: 30, vol: 0.25, type: "call", _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": {
      "dte": 30,
      "vol": 0.25,
      "spot": 100,
      "type": "call",
      "strike": 105,
      "_apiKey": "your-flashalpha-api-key"
    },
    "name": "flashalpha_greeks"
  }
}

Input Schema

NameRequiredDescriptionDefault
dteYesDays to expiration, e.g. 30
volYesImplied volatility as a decimal (sigma), e.g. 0.25 for 25%
rateNoRisk-free interest rate as a decimal (optional), e.g. 0.05 for 5%
spotYesCurrent underlying (spot) price, e.g. 100
typeYesOption type: "call" or "put"
strikeYesOption strike price, e.g. 105
_apiKeyYesFlashAlpha API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by naming the model (BSM) and enumerating returns, but it does not say what happens when optional 'rate' is omitted, whether theta is per-day, or how failures surface.

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 with the tool's identity, then inputs, then outputs, then a single compact example call. Slightly dense in one sentence, and the parenthetical about higher-order greeks is hedged wording, but nothing is truly wasteful.

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?

With no output schema, the description partially compensates by listing delta, gamma, theta and vega as returns. However, for a 7-parameter financial calculator it leaves gaps around the optional risk-free rate's default, output units/conventions, and whether higher-order greeks are reliably present.

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 every parameter including the optional 'rate' and the required '_apiKey' is already documented in the schema. The description restates the core five parameters and gives one example, but adds no units or constraints beyond what the schema provides, so the baseline of 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?

States a specific verb+resource: a Black-Scholes (BSM) greeks calculator that takes spot, strike, DTE, vol and option type and returns delta/gamma/theta/vega. This is clearly distinct in kind from siblings like flashalpha_gex or flashalpha_iv, but the description never explicitly contrasts itself with them.

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 implied by the required inputs and a worked example call, so an agent can infer 'give me greeks for one contract'. There is no explicit statement of when to prefer this over the sibling pricing/IV tools, and no exclusions or preconditions (e.g. valid DTE range, needing an API key) beyond the required-param list.

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.