finance-pulse
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | Yes | Your RapidAPI key subscribed to the Finance Pulse plan. Create a RapidAPI account, subscribe to a plan (Basic is free), then copy your X-RapidAPI-Key from the API's page on RapidAPI. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_statementsA | Search extracted news statements, newest first. Use for "what is the news saying about X". symbol: ticker or entity code, e.g. NVDA; comma-separate several (OR), no spaces inside a code. importance_min=high keeps only key facts. source_type=news leaves out speculative analysis and reddit. since/until: ISO-8601 times on the article's publication time, e.g. 2026-10-01T00:00:00Z. limit: 1-100. Pass next_cursor back as cursor for the next page (null means no more). |
| trendingA | The developments most outlets are reporting. Use for "what is moving / what is the big news right now". kind=live: the last 2 hours; kind=slot: the top stories of each 2-hour slot over the last 7 days.
For the whole day rather than the last 2 hours, use find_topics with sort=velocity (last 24 hours).
kind=slot lists up to 10 stories per slot over 7 days, so raise limit when you need more than the top of it;
each item's |
| get_topicA | One development in full: its counts, how many of its statements come from news, speculative analysis and reddit (source_mix), and its 20 newest statements, each with its outlet. For older statements call search_statements with topic_id and the returned statements_cursor as cursor. |
| find_topicsB | List developments for a symbol, sector or theme. sort=velocity: most statements in the last 24 hours; size: most statements in the window; recent: latest statement first. symbol: comma-separate several (OR). |
| themesA | The standing subjects the news is grouped into (Energy, Central banks & rates, ...), each with its number of developments and statements, 24-hour volume, distinct sources and sentiment counts. With symbol or sector: only the themes that have statements about it; the counts are still those of the whole theme, so use search_statements with theme_id and symbol for the symbol's own statements. Use the returned id as theme_id in the other tools. |
| sentiment_seriesA | News volume and sentiment over time for exactly one of symbol, sector, theme_id or topic_id. Each bucket: t (UTC start), count, bullish, bearish, neutral, sources (distinct outlets) and
score = (bullish - bearish) / count. Buckets with no statements are omitted here. Unless |
| screenA | Rank symbols (or the 11 GICS sectors) by news attention. Use for "which tickers are suddenly in the news". period: d = last 24 hours, w = last 7 days, window = everything held. sort=change ranks by the rise in mentions against the previous period (not available for period=window; use sort=mentions there). Each row: mentions, topics, sources (distinct outlets), sentiment counts, score and change. Only for rank=symbols: sector limits the screen to one sector; min_mentions drops rarely mentioned codes; entity_kinds narrows the kind of entity, comma-separated, from: equity, etf, index, rate, fx, crypto, commodity, org, private, country. Without it the list mixes companies with rates, commodities and central banks; pass "equity,etf" for tradable tickers. |
| referenceA | The data's window and size, known data incidents (outages, delays), the themes with their ids, and the accepted sector, sentiment, importance, source-type and entity-kind values. Call once; it rarely changes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes: search_statements for raw news search, get_topic for a single development, trending for top stories, find_topics for listing developments, themes for standing subjects, sentiment_series for time series, screen for ranking symbols, and reference for metadata. However, trending and find_topics overlap somewhat in surfacing current developments, and themes/reference both expose theme-related metadata, which could cause occasional misselection.
Names mix verb_noun patterns (get_topic, search_statements, find_topics, sentiment_series) with noun-only names (trending, themes, screen, reference). The set is still readable, but the convention is not predictable throughout.
Eight tools is well-scoped for a finance news analytics server. Each tool covers a distinct analytical need without obvious redundancy or bloat.
The surface covers search, topic discovery, trending, themes, sentiment series, ranking, and reference metadata, which supports most analysis workflows. Minor gaps exist, such as no direct tool for retrieving full article content or outlet-level details, but agents can work around these via existing tools.