Newsnow MCP Server

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation2/5
Multiple tools have overlapping purposes that could cause confusion. For example, 'top_news_powered_by_google' and 'top_news_powered_by_duck_duck_go' both retrieve top news but from different sources, while 'top_news_by_category_powered_by_google', 'top_news_by_locationpowered_by_google', and 'top_news_by_site_powered_by_google' all fetch top news with different filters. The descriptions don't clearly differentiate when to use each tool, leading to potential misselection.
Naming Consistency3/5
The naming shows mixed conventions with some consistency issues. Most tools follow a 'top_news_by_X_powered_by_Y' pattern, but there are deviations like 'news_api_v2_powered_by_google' (using 'api_v2' instead of 'by_X'), 'top_news_by_locationpowered_by_google' (missing underscore between 'location' and 'powered'), and 'top_news_pwered_by_google' (typo 'pwered' instead of 'powered'). The 'ping_test' tool also breaks the pattern entirely.
Tool Count4/5
With 7 tools, the count is reasonable for a news server scope. It covers various news retrieval methods (by date, category, location, site, source) which justifies having multiple tools. However, the overlap between tools suggests some consolidation might improve coherence without reducing functionality.
Completeness3/5
The server covers basic news retrieval operations with different filters and sources, but there are notable gaps. There's no clear update, delete, or management functionality for news items (though this may be appropriate for a read-only news service). More importantly, the surface feels fragmented with multiple similar tools rather than a unified approach, which could leave agents uncertain about the optimal tool for specific scenarios.
Average 2.3/5 across 7 of 7 tools scored. Lowest: 1.6/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI is passing
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. 'ping' gives no insight into whether this is a read/write operation, its side effects, authentication needs, rate limits, or expected behavior, making it completely opaque.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
While 'ping' is extremely concise, it is under-specified rather than efficiently informative. A single word fails to convey necessary details, making this brevity detrimental rather than helpful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's unknown complexity and lack of annotations or output schema, the description is completely inadequate. It provides no context about what 'ping' does, its purpose, or expected outcomes, leaving the agent unable to use it effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, but this is acceptable as there are no parameters to explain, warranting a baseline score of 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'ping' is a tautology that merely restates the tool name without explaining what the tool actually does. It provides no specific verb or resource, making it impossible to understand the tool's purpose or distinguish it from any other tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or comparison with sibling tools, leaving the agent with no usage instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden but discloses no behavioral traits. It doesn't mention data sources, rate limits, authentication needs, or what 'Top News' means (e.g., recency, popularity). This leaves the agent with insufficient information to predict tool behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise ('Get Top News'), which is efficient but under-specified. It lacks structure or elaboration that could provide necessary context, making it more sparse than appropriately concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and multiple sibling tools, the description is incomplete. It fails to explain what 'Top News' includes, how it's sourced from DuckDuckGo, or differentiate it from similar tools, leaving significant gaps for an agent to understand its use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter details, but this is acceptable given the absence of parameters, aligning with the baseline for zero parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Get Top News' restates the tool name 'top_news_powered_by_duck_duck_go' with minimal elaboration, making it tautological. It specifies the verb 'Get' and resource 'Top News' but lacks detail on what 'Top News' entails or how it differs from sibling tools like 'top_news_by_category_powered_by_google'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as 'top_news_by_category_powered_by_google' or 'news_api_v2_powered_by_google'. The description offers no context, prerequisites, or exclusions, leaving usage entirely ambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavioral traits. It fails to describe any behavior—such as whether it's a read-only operation, its rate limits, authentication needs, or what it returns (e.g., news headlines, articles). The description adds no value beyond the name, leaving the agent uninformed about how the tool functions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise (one phrase) but under-specified—it lacks essential details like purpose and behavior, making it inefficient rather than appropriately brief. While front-loaded, it does not earn its place by providing useful information, resulting in a mediocre score.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and low complexity (0 parameters), the description is incomplete. It does not explain what the tool does, when to use it, or what it returns, failing to provide basic contextual information needed for an agent to understand and invoke the tool effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters with 100% schema description coverage, so no parameter information is needed. The description does not add or detract from parameter semantics, which is appropriate. Baseline is 4 for zero parameters, as there is nothing to compensate for.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'TOP NEWS (pwered by Google)' restates the tool name with a minor typo ('pwered' instead of 'powered'), making it largely tautological. It specifies the resource ('news') and source ('Google') but lacks a clear verb indicating what the tool does (e.g., 'fetch', 'retrieve', or 'list'). It does not differentiate from siblings like 'top_news_by_category_powered_by_google' or 'top_news_powered_by_duck_duck_go'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. It does not mention context, prerequisites, or exclusions, nor does it reference sibling tools like 'top_news_by_category_powered_by_google' or 'top_news_powered_by_duck_duck_go' for comparison. This leaves the agent without direction on tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It hints at behavioral traits like returning 'more detailed news, top images etc' when 'more_information: true' is set, but this contradicts the schema (which has no parameters). This creates confusion about how to control output. It doesn't disclose other behaviors such as rate limits, authentication needs, or data freshness.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is brief but poorly structured and front-loaded with confusing information about a non-existent parameter. The two clauses are disjointed: one about setting a parameter and another about the tool's purpose. It wastes space on irrelevant details, reducing efficiency, though it's not overly verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (news retrieval with potential filtering by site) and lack of annotations and output schema, the description is incomplete. It fails to explain what 'by site' entails, how results are returned, or what 'top news' means (e.g., recency, popularity). The misleading parameter reference adds to the inadequacy, leaving gaps for an AI agent to use it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description attempts to add semantics by mentioning 'set more_information: true', but this is misleading since no such parameter exists. However, with zero parameters, the baseline is 4, as the description doesn't need to compensate for schema gaps, though the misleading part slightly reduces clarity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states 'get top news by site' which provides a basic purpose (verb+resource), but it's vague about what 'by site' means (e.g., filtering by website domain, aggregating from specific sites). It doesn't distinguish from siblings like 'top_news_by_category_powered_by_google' or 'top_news_by_locationpowered_by_google', leaving ambiguity in scope. The first part about 'set more_information: true' is confusing since there are no parameters in the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives is provided. The mention of 'set more_information: true' implies a parameter that doesn't exist in the schema, which could mislead usage. There's no context on prerequisites, timing, or comparisons to sibling tools like 'news_api_v2_powered_by_google' or 'top_news_powered_by_duck_duck_go'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It mentions date format and filtering options, but lacks critical behavioral details such as rate limits, authentication needs, pagination, error handling, or what 'latest news' entails (e.g., recency, quantity). The contact info for queries/bugs is a minor addition but insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is poorly structured and verbose with run-on sentences, unclear formatting (e.g., 'from date' to 'To date'), and includes extraneous contact information that doesn't aid tool selection. It's not front-loaded and wastes space on non-essential details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and an empty input schema, the description is incomplete. It fails to explain return values, error cases, or operational constraints like rate limits, making it inadequate for a news API tool that likely involves network calls and data filtering.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so no parameters are documented in the schema. The description compensates by explaining implied parameters like date ranges, categories, and location, adding meaningful semantics beyond the empty schema. However, it doesn't specify if these are query parameters or how to pass them.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool 'get[s] news' with date range and filtering capabilities, which provides a general purpose. However, it's vague about the exact resource (e.g., news articles, headlines) and doesn't clearly distinguish from siblings like 'top_news_by_category_powered_by_google', which also filters news by category.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for time-bounded news or latest news, but offers no explicit guidance on when to use this tool versus alternatives like sibling tools for category- or location-based filtering. No exclusions or prerequisites are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden but adds minimal behavioral insight. It implies a read operation ('get') but doesn't disclose traits like rate limits, authentication needs, data freshness, or what 'top' means (e.g., recency, popularity). This is inadequate for a tool with zero annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient phrase with no wasted words. However, it's under-specified rather than concise—it lacks necessary detail for clarity, but structurally it's front-loaded and minimal.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and a vague purpose, the description is incomplete. It doesn't explain what 'top news' entails, how locations are used, or what the return format might be. For a news-fetching tool with sibling alternatives, more context is needed to guide effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param details, which is fine, but it could hint at implicit inputs (e.g., location source). Baseline is 4 for zero params, as the schema fully covers the absence.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'get top news by locations' states the basic purpose with a verb ('get') and resource ('top news'), but it's vague about what 'by locations' means—does it filter, aggregate, or something else? It doesn't distinguish from siblings like 'top_news_by_category_powered_by_google' or 'top_news_by_site_powered_by_google', leaving ambiguity in scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. With siblings like 'top_news_by_category_powered_by_google' and 'top_news_by_site_powered_by_google', the description lacks any indication of context, prerequisites, or exclusions, leaving the agent to guess based on names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the categories available but doesn't describe what 'top news' means (e.g., recency, popularity), how many items are returned, whether there are rate limits, or any authentication requirements. This leaves significant gaps in understanding the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is brief and to the point, consisting of two parts: a list of categories and the core function. However, it lacks structure (e.g., no clear separation between categories and usage) and could be more front-loaded by stating the purpose first. It's concise but not optimally organized.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., news headlines, summaries, links), how results are formatted, or any error conditions. For a news-fetching tool, this leaves the agent without enough information to use it effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so there are no parameters to document. The description adds value by listing the available categories (WORLD, NATION, etc.), which provides essential context for using the tool, even though these aren't formal parameters in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'get top news by category' with a specific list of categories provided. It uses a clear verb ('get') and resource ('top news'), but doesn't explicitly distinguish it from sibling tools like 'top_news_by_location' or 'top_news_by_site' beyond the 'by category' qualifier.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It lists categories but doesn't explain why one would choose category-based news over location-based or site-based news from the sibling tools, nor does it mention any prerequisites or constraints for usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![bachai-newsnow MCP server](https://glama.ai/mcp/servers/BACH-AI-Tools/bachai-newsnow/badges/card.svg)](https://glama.ai/mcp/servers/BACH-AI-Tools/bachai-newsnow)

Score Badge

Copy to your README.md:

[![bachai-newsnow MCP server](https://glama.ai/mcp/servers/BACH-AI-Tools/bachai-newsnow/badges/score.svg)](https://glama.ai/mcp/servers/BACH-AI-Tools/bachai-newsnow)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/bachai-newsnow'

If you have feedback or need assistance with the MCP directory API, please join our Discord server