positive-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sentimentA | START HERE. Current AI news-sentiment reading for Bitcoin, Gold or crude Oil on a −1..+1 scale, rebuilt every hour from that hour's news coverage — plus the three heaviest narratives behind it, so one call answers both what the mood is and why. Also returns the measurement time and expiry, what the number is made of (news + X chatter + Polymarket odds), 1h/24h/7d changes, and a ready-to-use citation line. Covers BTC, GOLD and OIL only; any other asset returns an explicit error rather than a substitute. It measures the tone of coverage, not price, and does not forecast price. |
| get_narrativesA | The full set of stories behind the number — this is where most of the value is. Recurring narratives the hour's coverage groups into, each with its own sentiment, |
| get_historyA | Sentiment over the last seven days — reach for this only to tell a normal reading from an outlier, since today's number often only means something next to yesterday's. Daily by default: one point per day with close/avg/min/max, which answers that question at about a sixth of the payload. Pass granularity 'hourly' for every run only when the shape inside a day matters. Seven days is the full public window. |
| get_sourcesA | The evidence — reach for it to VERIFY, not to explain. Every headline that went into the current reading, each with its own score, age, publisher and a link to the original article. Use it to check a specific claim or to find the primary reporting behind a move; for the explanation itself, narratives are cheaper and clearer. Per-article weight is deliberately not published — weight is published where it is stable, as narrative |
| compare_assetsA | All three readings (Bitcoin, Gold, Oil) in one call, ranked most bullish first, each with its own measurement time. Use when asked where the news mood is best or worst, or to pick an asset before going deeper with get_sentiment — three separate calls for the same picture is the most common waste. |
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 5 tools
Each tool targets a clearly distinct aspect: current sentiment, historical data, narrative details, source headlines, and cross-asset comparison. No two tools overlap in purpose, and descriptions explicitly differentiate when to use each, such as get_sentiment for the current reading vs. get_narratives for full stories.
All tool names follow a consistent verb_noun pattern in snake_case: get_sentiment, get_history, get_narratives, get_sources, and compare_assets. The first four use 'get_' and the last uses 'compare_', which is still a verb_noun pattern, maintaining a predictable and uniform style.
Five tools is well-scoped for this sentiment analysis server covering three assets. Each tool adds meaningful functionality without redundancy, and the count fits comfortably within the ideal 3-15 range for a focused API.
The tool surface covers all major aspects of sentiment analysis: current reading, historical trends, narrative breakdown, source evidence, and multi-asset comparison. Given the stated domain (news-sentiment for BTC, GOLD, OIL), there are no obvious gaps—the descriptions even mention users can follow up with more granular calls as needed.