Skip to main content
Glama
JerBouma

Finance Toolkit

by JerBouma

discovery

Read-onlyIdempotent

Discover market opportunities with stock screeners, gainers/losers, sector performance, IPO calendars, and more—no tickers or countries required.

Instructions

Market discovery tools (lists of stocks/ETFs/cryptocurrencies, stock screener, gainers, losers, sector performance, earnings/dividend calendars). No tickers or countries needed.

Available indicators: get_biggest_gainers, get_biggest_losers, get_commodity_list, get_crypto_list, get_crypto_news, get_delisted_stocks, get_etf_list, get_forex_list, get_forex_news, get_general_news, get_index_list, get_industry_pe, get_industry_performance, get_ipo_calendar, get_ipo_disclosures, get_ipo_prospectuses, get_mergers_acquisitions_latest, get_most_active_stocks, get_press_releases, get_sector_pe, get_sector_performance, get_sectors_performance, get_stock_list, get_stock_news, get_stock_screener, get_stock_shares_float, get_stock_splits_calendar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoValue for date.
pageNoValue for page.
limitNoValue for limit.
pagesNoValue for pages.
is_etfNoValue for is_etf.
sectorNoValue for sector.
industryNoValue for industry.
indicatorYesName of the specific metric to calculate, e.g. 'get_asset_turnover_ratio'. Required — omitting it returns the list of available indicators.
beta_lowerNoValue for beta_lower.
beta_higherNoValue for beta_higher.
price_lowerNoValue for price_lower.
price_higherNoValue for price_higher.
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.
volume_lowerNoValue for volume_lower.
volume_higherNoValue for volume_higher.
dividend_lowerNoValue for dividend_lower.
dividend_higherNoValue for dividend_higher.
market_cap_lowerNoValue for market_cap_lower.
market_cap_higherNoValue for market_cap_higher.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint. The description adds value by listing specific indicators and clarifying the scope (no tickers). No contradiction 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 front-loaded with purpose, but the exhaustive list of indicators is redundant with the enum in schema and makes it longer than necessary.

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 complexity (19 parameters), the description lacks guidance on how to combine parameters for specific tasks like stock screening, which is mentioned but not elaborated. Output schema exists, so return values are covered.

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 has 100% coverage with descriptions, though most are generic 'Value for ...'. The description does not add extra parameter semantics beyond the schema baseline.

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 identifies the tool as providing market discovery data (lists, screener, gainers, etc.) and explicitly states 'No tickers or countries needed', distinguishing it from sibling tools that require specific instruments or focus on specific metrics.

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?

The description says 'No tickers or countries needed' implying when to use, and lists available indicators. However, it does not explicitly state when NOT to use or provide clear alternatives among the many sibling tools.

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