Skip to main content
Glama
JerBouma

Finance Toolkit

by JerBouma

fixed_income

Read-onlyIdempotent

Calculate bond duration, present value, yield-to-maturity, and derivative prices by providing bond and derivative parameters directly. Solve fixed income valuation problems without tickers or countries.

Instructions

Bond and derivative valuation calculations (bond duration, present value, yield-to-maturity, derivative pricing). No tickers or countries needed — provide bond/derivative parameters (e.g. face_value, coupon_rate, maturity) directly as arguments.

Available indicators: get_derivative_price, get_duration, get_present_value, get_yield_to_maturity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guessNoValue for guess.
modelNoValue for model.black
tenorNoValue for tenor.
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-07-14
notionalNoValue for notional.
countriesNoComma-separated country names, e.g. 'United States,Germany,Japan'.
frequencyNoValue for frequency.
indicatorYesName of the specific metric to calculate, e.g. 'get_asset_turnover_ratio'. Required — omitting it returns the list of available indicators.
par_valueNoValue for par_value.
quarterlyNoReturn quarterly data instead of annual when True.
toleranceNoValue for tolerance.
bond_priceNoClean price of the bond per 100 face value.
start_dateNoStart of the date range in YYYY-MM-DD format.2021-07-15
volatilityNoValue for volatility.
coupon_rateNoAnnual coupon rate as a decimal, e.g. 0.05 for 5 %.
is_receiverNoValue for is_receiver.
strike_rateNoOption strike price.
forward_rateNoValue for forward_rate.
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.
duration_typeNoValue for duration_type.modified
include_payoffNoValue for include_payoff.
max_iterationsNoValue for max_iterations.
risk_free_rateNoValue for risk_free_rate.
show_input_infoNoValue for show_input_info.
payment_frequencyNoValue for payment_frequency.
years_to_maturityNoYears remaining until the bond matures.
yield_to_maturityNoValue for yield_to_maturity.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds that no tickers or countries are needed and provides a hint about using show_columns to reduce output, which goes 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 concise and front-loaded with the main purpose. Some redundancy exists (listing indicators again), but overall it is well-structured.

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?

Given 27 parameters, high schema coverage, and an output schema, the description covers the core functionality and usage hints. It does not explain return values but output schema exists.

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 description coverage is 100%, so baseline is 3. The description lists the indicators but does not add meaningful semantics for most parameters beyond what the schema provides.

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 handles bond and derivative valuation calculations, listing specific indicators. It distinguishes from sibling tools which cover other financial domains.

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 implies usage for bond/derivative valuations but does not explicitly compare to sibling tools or state when not to use it. It mentions omitting indicator to get a list, providing some guidance.

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