Skip to main content
Glama
JerBouma

Finance Toolkit

by JerBouma

rates

Read-onlyIdempotent

Retrieve central bank policy rates, government bond yields, EURIBOR, and other interest rate indicators for specified countries with options for date ranges, rolling averages, and growth rates.

Instructions

Interest rate data (central bank policy rates, short/long-term rates, government bond yields, ICE BofA corporate bond series, EURIBOR, ECB rates, Federal Reserve rates). Requires countries='United States' — use comma-separated values for multiple countries. Do NOT use tickers= for this tool. Supports start_date/end_date and quarterly=true. The central bank policy rate and short/long-term rate indicators additionally support rolling=N (moving-average smoothing) and trailing=N (trailing N-period sum).

Available indicators: get_central_bank_policy_rate, get_short_term_interest_rate, get_long_term_interest_rate, get_government_bond_yield, get_euribor_rates, get_european_central_bank_rates, get_federal_reserve_rates, get_ice_bofa_effective_yield, get_ice_bofa_option_adjusted_spread, get_ice_bofa_total_return, get_ice_bofa_yield_to_worst.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lagNoNumber of periods to lag when computing growth rates.
rateNoValue for rate.
growthNoReturn period-over-period growth rates instead of absolute values.
periodNoObservation frequency, e.g. 'monthly', 'quarterly', or 'annual'.
nominalNoValue for nominal.
rollingNoRolling window size in number of periods. When set, the metric is computed over a smoothly overlapping trailing window across the full history (e.g. period='monthly' and rolling=6 gives a rolling 6-month value) instead of one value per period, or (for economics indicators) a simple moving average used to smooth the raw series.
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-07-14
maturityNoValue for maturity.
trailingNoTrailing window size in number of periods. Sums the raw values over the trailing N periods (e.g. trailing=4 on quarterly data gives a trailing-4-quarter / TTM-style sum) instead of returning one value per period.
countriesNoComma-separated country names, e.g. 'United States,Germany,Japan'.
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.
maturitiesNoComma-separated bond maturity labels, e.g. '3month,2year,10year'.
short_termNoValue for short_term.
start_dateNoStart of the date range in YYYY-MM-DD format.2021-07-15
gmdb_sourceNoUse the OECD Global Macro Data Bank as the data source when True.
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.

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, openWorldHint, idempotentHint. The description adds behavioral details such as requiring 'countries' and forbidding 'tickers', plus mentioning optional parameters for smoothing and trailing. No contradictions with annotations.

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 a single paragraph that mixes purpose, usage constraints, and indicator list. It front-loads the purpose, but the list of indicators is redundant with the schema's enum. Could be more concise by omitting the full list.

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?

For a tool with 18 parameters and complex usage, the description gives a good overview of the main use cases and constraints. The output schema exists, so return format details are not needed. It covers essential context for selecting and invoking the tool.

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 the description adds limited value for parameters. It highlights key parameters (countries, tickers, dates, quarterly, rolling, trailing) and lists indicator options, but these are also documented in the schema. Does not provide deeper meaning beyond the schema.

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 identifies the tool as providing interest rate data, listing specific types (central bank policy rates, bond yields, EURIBOR, etc.). It states what the tool does, but does not explicitly differentiate from sibling tools like 'fixed_income' or 'government', which could overlap.

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?

Provides explicit usage instructions: requires 'countries='United States'', do not use 'tickers=', and supports 'start_date'/'end_date', 'quarterly', 'rolling', 'trailing'. It also lists available indicators. However, it does not specify when to use this tool versus alternatives (e.g., when to use 'rates' vs 'fixed_income').

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