Skip to main content
Glama
JerBouma

Finance Toolkit

by JerBouma

government

Read-onlyIdempotent

Get country fiscal metrics: debt, deficit, expenditure, revenue, tax revenue, and trust. Pass comma-separated country names, choose annual/quarterly, and optional rolling/trailing windows.

Instructions

Government fiscal metrics by country (debt, deficit, expenditure, revenue, tax revenue, trust in government). 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. Supports rolling=N (moving-average smoothing) and trailing=N (trailing N-period sum, e.g. a trailing-4-quarter sum) on the raw series.

Available indicators: get_government_debt, get_government_debt_to_gdp_ratio, get_government_deficit, get_government_deficit_to_gdp_ratio, get_government_expenditure, get_government_expenditure_to_gdp_ratio, get_government_revenue, get_government_revenue_to_gdp_ratio, get_government_tax_revenue, get_government_tax_revenue_to_gdp_ratio, get_trust_in_government.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lagNoNumber of periods to lag when computing growth rates.
growthNoReturn period-over-period growth rates instead of absolute values.
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-08-19
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.
start_dateNoStart of the date range in YYYY-MM-DD format.2021-08-20
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=true and destructiveHint=false, covering the safety profile. Description adds meaningful behavioral info: mandatory countries constraint, prohibition on tickers, and explains rolling vs trailing data transformations. No contradictions. Could mention pagination or output size limits but output schema exists.

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?

Two concise paragraphs. First paragraph explains purpose and key constraints; second lists indicators. Front-loaded. No fluff. The indicator list is redundant with schema enum but serves as quick reference. Sufficiently concise.

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

Completeness5/5

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

Given the high schema coverage and output schema present, the description is complete. It covers all critical usage constraints (countries required, tickers forbidden, date/frequency options) and clarifies the main non-obvious parameters (rolling vs trailing). No gaps.

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 baseline 3. However, description adds critical information: countries must be provided (default empty but required), tickers= not used, rolling=N and trailing=N semantics clarified (moving-average vs trailing sum), and shows comma-separated example. This elevates beyond schema.

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 specifies the tool's function: government fiscal metrics by country (debt, deficit, expenditure, revenue, tax revenue). It lists all 11 available indicators explicitlyaining any ambiguity about scope. The verb 'get' and the resource 'fiscal metrics' with country parameters is specific.

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 conditions: requires countries='United States' (with comma-separated for multiple), supports date range and quarterly, and explicitly warns NOT to use tickers=. This gives strong practical usage guidance. Minor gap: doesn't mention when to prefer this over sibling economic tools, but that's acceptable given the tool's clear domain.

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