@wopal/mcp-server-hotnews
OfficialServer 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_hot_newsC | Get hot trending lists from various platforms |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool has a clear, distinct purpose focused on retrieving hot trending news from various platforms, leaving no ambiguity for an agent to misselect between tools.
The naming follows a consistent verb_noun pattern with 'get_hot_news'. Since there is only one tool, it inherently maintains perfect consistency without any deviations or mixed conventions to evaluate.
A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete or overly narrow scope. For a news-related server, one tool feels thin and inadequate for covering typical operations like searching, filtering, or managing news content.
The tool surface is severely incomplete for a news domain. While 'get_hot_news' provides retrieval, there are obvious gaps such as searching for specific news, filtering by categories or platforms, or accessing detailed articles, which are essential for comprehensive news handling and will likely cause agent failures in broader tasks.