Skip to main content
Glama
JerBouma

Finance Toolkit

quant_options

Read-onlyIdempotent

Compute option pricing and Greeks using Black-Scholes, binomial tree, and risk metrics like delta, gamma, and implied volatility for specified 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
indicatorYesName of the specific metric to calculate, e.g. 'get_asset_turnover_ratio'. Required — omitting it returns the list of available indicators.
tickersNoComma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
start_dateNoStart of the date range in YYYY-MM-DD format.2021-06-22
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-06-21
quarterlyNoReturn quarterly data instead of annual when True.
benchmark_tickerNoTicker used as the market benchmark, e.g. 'SPY' or '^GSPC'.SPY
put_optionNoValue for put_option.
american_optionNoValue for american_option.
strike_price_rangeNoValue for strike_price_range.
strike_step_sizeNoValue for strike_step_size.
time_to_expirationNoValue for time_to_expiration.
timestepsNoValue for timesteps.
risk_free_rateNoValue for risk_free_rate.
dividend_yieldNoValue for dividend_yield.
show_input_infoNoValue for show_input_info.
roundingNoNumber of decimal places to round results to.
expiration_time_rangeNoValue for expiration_time_range.
expiration_dateNoValue for expiration_date.
show_expiration_datesNoValue for show_expiration_dates.
show_unique_combinationsNoValue for show_unique_combinations.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare read and idempotent hints. The description adds that it requires tickers and mentions specific models, but provides no additional behavioral context beyond annotations.

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 clear list of indicators. It is reasonably concise and front-loads the main purpose, though the list is lengthy.

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

Completeness2/5

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

With 20 parameters and many vague schema descriptions, the tool description lacks guidance on how to use the various indicators and parameters. Given the complexity, more explanation is needed.

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

Parameters2/5

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

Although schema coverage is 100%, many parameter descriptions are unhelpful (e.g., 'Value for put_option'). The tool description does not explain these parameters beyond mentioning tickers and indicator.

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 clearly states it provides option pricing and Greeks, and lists many specific indicators. However, it does not distinguish from sibling tools like quant_models or quant_performance, which could cause confusion.

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?

The description gives an example for tickers and notes that omitting indicator returns the list. But it does not specify when to use this tool versus alternatives, nor does it provide exclusions.

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