Skip to main content
Glama
JerBouma

Finance Toolkit

by JerBouma

options

Read-onlyIdempotent

Compute option pricing models and Greeks (Black-Scholes, binomial, delta, gamma, theta, vega, rho) and implied volatility for any ticker.

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-07-14
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-07-15
standardizeNoReturn the Z-Score (standard score) instead of the raw values, i.e. how many standard deviations each value is from the mean of its own series. When combined with growth=True, the growth values are standardized instead of the raw values.
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
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true. The description adds no behavioral context beyond that, but does not contradict the annotations. A score of 3 is appropriate as the description is neutral.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise but includes a lengthy list of all indicators, which could be condensed. The first sentence clearly states purpose, but the second sentence about tickers is misleading. Overall, it is acceptable but not optimized.

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?

Given the 21 parameters, 100% schema coverage, and presence of an output schema, the description provides basic context. However, it omits guidance on parameter combinations, how different indicators affect output, and fails to clarify the tickers requirement inconsistency, leaving gaps.

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% with detailed parameter descriptions, so the baseline is 3. The tool description adds no new parameter information; it even contradicts the schema by stating tickers as required when it is optional. The indicator enum is listed but without explanation of when each indicator is suitable.

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 'Option pricing and Greeks' and lists specific indicators, making the purpose evident. It distinguishes from broad market_data tools by focusing on options-specific metrics. However, the title is null and the name 'options' is vague without context.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings like 'volatility' or 'risk'. It mentions requiring tickers but contradicts the schema. No exclusions or alternatives are provided, leaving the agent to infer usage.

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