News MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_newsB | Search for news articles using multiple news APIs with automatic failover. The system intelligently switches between different news APIs when one reaches its limit or fails. |
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 ambiguity or overlap between tools. The tool's purpose is clearly defined as searching for news articles, and no other tools exist to cause confusion.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'search_news' follows a clear verb_noun pattern, which is appropriate for its function.
A single tool is too few for a server named 'News MCP Server', which implies a broader scope for news-related operations. While the tool is well-described, the server lacks basic operations like fetching headlines, categories, or article details, making it feel incomplete and under-scoped.
The server is severely incomplete for a news domain. It only provides search functionality, missing essential operations such as retrieving top headlines, filtering by category or source, or accessing full article content. This will likely cause agent failures when trying to perform common news-related tasks.