crypto_news_research_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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_today_crypto_newsA | Collect crypto news for a YYYY-MM-DD date in Asia/Seoul; live RSS or explicit demo fixtures. |
| summarize_crypto_newsB | Create an extractive news digest with short feed excerpts, source links, and detected coin mentions. |
| collect_article_evidenceC | Read public article bodies into source-linked paragraph evidence; keep failures explicit and demo bodies separate. |
| analyze_crypto_insightsB | Build paragraph-grounded insight drafts separating reported observations, interpretations, counterpoints, and watch metrics. Uses explicit topic rules, not an LLM. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| crypto_news_brief | Prepare the crypto news research workflow for a date. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| news_sources | Read the configured crypto RSS publishers. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose in the news research pipeline: fetching raw news, creating an extractive summary, collecting article-body evidence, and building insight drafts. The descriptions reinforce these boundaries with specific outputs and methods, leaving little room for misselection.
All tool names follow a uniform verb_noun snake_case pattern (fetch_today_crypto_news, summarize_crypto_news, collect_article_evidence, analyze_crypto_insights). The verbs and objects are semantically aligned with each tool's function, making the naming predictable and readable.
With four tools, the server is well-scoped for a focused crypto news research workflow. Each tool represents a necessary step in the pipeline without redundancy, fitting comfortably within the ideal 3-15 tool range.
The tool set forms a coherent pipeline from fetching news to generating insight drafts, covering all core research steps. A minor gap is the absence of a dedicated search or filter tool, but agents can work around this by fetching specific dates, so no major dead ends exist.