Skip to main content
Glama
JerBouma

Finance Toolkit

options

Read-onlyIdempotent

Calculate option prices and Greeks using Black-Scholes and binomial models. Supports indicators like delta, gamma, theta, vega, rho, and implied volatility for stock tickers.

Instructions

Option pricing and Greeks (Black-Scholes model, binomial tree, delta, gamma, theta, vega, rho, implied volatility). Requires tickers='AAPL' — use comma-separated values for multiple tickers.

Available indicators: get_binomial_model, get_black_scholes_model, get_charm, get_color, get_delta, get_dual_delta, get_dual_gamma, get_epsilon, get_gamma, get_implied_volatility, get_lambda, get_option_chains, get_partial_derivative, get_rho, get_speed, get_stock_price_simulation, get_theta, get_ultima, get_vanna, get_vega, get_vera, get_veta, get_vomma, get_zomma.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickersNoComma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-06-27
indicatorYesName of the specific metric to calculate, e.g. 'get_asset_turnover_ratio'. Required — omitting it returns the list of available indicators.
quarterlyNoReturn quarterly data instead of annual when True.
timestepsNoValue for timesteps.
put_optionNoValue for put_option.
start_dateNoStart of the date range in YYYY-MM-DD format.2021-06-28
show_columnsNoComma-separated names to filter the output. For historical data use the key names visible in any response record (e.g. 'Close,Volume,Return'). For financial statements use the 'metric' field values from the response (e.g. 'Revenue,Net Income,EBITDA'). Call the tool once without this parameter to see all available names, then repeat with show_columns to reduce response size and token usage.
dividend_yieldNoValue for dividend_yield.
risk_free_rateNoValue for risk_free_rate.
american_optionNoValue for american_option.
expiration_dateNoValue for expiration_date.
show_input_infoNoValue for show_input_info.
benchmark_tickerNoTicker used as the market benchmark, e.g. 'SPY' or '^GSPC'.SPY
strike_step_sizeNoValue for strike_step_size.
strike_price_rangeNoValue for strike_price_range.
time_to_expirationNoValue for time_to_expiration.
expiration_time_rangeNoValue for expiration_time_range.
show_expiration_datesNoValue for show_expiration_dates.
show_unique_combinationsNoValue for show_unique_combinations.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating safe, repeatable calls. The description adds that calling without an indicator returns a list of available indicators, which is a behavioral detail not in annotations. No contradictions.

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 description is a single paragraph with a list of indicators, efficient and front-loaded with purpose. It could be more structured (e.g., separate sections), but it's concise and readable.

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?

With an output schema present and 100% parameter description coverage, the description covers the main functionality and usage hints. It does not explain all parameter interactions, but the schema individually describes them. Adequate for the tool's complexity.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by emphasizing the required 'indicator' parameter and listing all indicators explicitly, beyond the schema's enum. It also highlights tickers format. This compensates for the large number of parameters.

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 clearly states it provides option pricing and Greeks using Black-Scholes and binomial tree models, specifying verb (compute) and resource (option metrics). Among siblings covering various financial categories, 'options' is uniquely focused on options, so no confusion.

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 gives explicit instructions: requires tickers, use comma-separated, and mentions that omitting the indicator returns a list. It implies when to use (option analysis) but does not explicitly state when not to use or provide alternatives, but the context of sibling tools makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JerBouma/FinanceToolkit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server