OpenNews MCP

Server Quality Checklist

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

Latest release: v0.1.0
Disambiguation4/5
Most tools have distinct purposes with clear boundaries, such as get_high_score_news for highly-rated articles and search_news_by_coin for coin-specific searches. However, some overlap exists between search_news and search_news_advanced, where the advanced version could potentially cover the basic search functionality, which might cause minor confusion.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with snake_case, such as get_high_score_news, search_news_by_coin, and subscribe_latest_news. The naming is predictable and readable throughout the set, making it easy for agents to understand the actions and targets.
Tool Count5/5
With 11 tools, the server is well-scoped for crypto news retrieval and filtering. Each tool serves a specific purpose, such as filtering by score, source, or coin, and the count supports comprehensive coverage without being overwhelming for the domain.
Completeness5/5
The tool set provides complete coverage for crypto news operations, including retrieval by various filters (score, recency, engine, signal, source, coin, keyword), listing of sources and types, advanced search, and real-time subscription. There are no obvious gaps, and agents can perform all expected news-related tasks.
Average 3.6/5 across 11 of 11 tools scored. Lowest: 3/5.
See the Tool Scores section below for per-tool breakdowns.
- 0 of 1 community issues answered or closed in the last 6 months
- 11 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
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

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. It mentions the tool searches 'by keyword in text content,' which implies a text-based search, but doesn't disclose behavioral traits like rate limits, authentication needs, response format, pagination, or what 'crypto news' encompasses (e.g., sources, time range). For a search tool with zero annotation coverage, this leaves significant gaps.
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 appropriately sized and front-loaded, with the core purpose stated first in a clear sentence. The additional parameter details are concise and relevant. There's minimal waste, though the structure could be slightly improved by integrating parameter info more seamlessly.
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 complexity of a search tool with no annotations, no output schema, and multiple sibling tools, the description is incomplete. It lacks information on return values (e.g., what fields are included in results), error handling, and how it differs from other search tools. This makes it inadequate for an agent to use the tool effectively in context.
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 description adds meaningful context beyond the input schema. The schema has 0% description coverage, providing only titles and types. The description explains that 'keyword' is a 'Search term (e.g. "bitcoin", "SEC", "ETF")' and 'limit' has a 'default 10, max 100,' which clarifies usage and constraints not in the schema. However, it doesn't fully detail all parameter nuances (e.g., keyword matching rules).
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: 'Search crypto news by keyword in text content.' This specifies the verb (search), resource (crypto news), and scope (by keyword in text content). However, it doesn't explicitly differentiate from siblings like 'search_news_advanced' or 'search_news_by_coin,' which would be needed for a perfect score.
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. With multiple sibling tools like 'search_news_advanced' and 'search_news_by_coin,' there's no indication of when this simpler keyword search is preferred or what limitations it has compared to more advanced options.
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 default and max values for 'limit', which is useful behavioral context. However, it doesn't disclose other traits like rate limits, authentication needs, pagination, response format, or error handling. For a tool with no annotations, this leaves significant gaps in understanding its behavior.
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 appropriately sized with three sentences: purpose statement, engine type list, and parameter details. It's front-loaded with the main purpose. No wasted words, though the structure could be slightly improved by integrating the engine list more smoothly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations and no output schema, the description provides basic purpose and parameter info but lacks details on return values, error cases, or operational constraints. It's minimally viable for a simple query tool but incomplete for full agent understanding, especially with multiple sibling tools available.
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?
Schema description coverage is 0%, so the description must compensate. It adds meaning by listing the five possible engine types ('news', 'listing', 'onchain', 'meme', 'market') and specifying default/max for 'limit', which aren't in the schema. This covers both parameters effectively, though it could explain what each engine type means semantically.
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 verb ('Get') and resource ('news articles'), and specifies filtering by 'engine type'. It distinguishes from some siblings (e.g., get_news_by_signal, get_news_by_source) by mentioning the engine filter, but doesn't explicitly differentiate from all alternatives like get_latest_news or search_news. The purpose is specific but could be more distinctive.
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 like get_news_by_signal or get_news_by_source. The description lists engine types but doesn't explain their meaning or when to choose this over other filtering methods. Usage is implied by the engine_type parameter but not contextualized relative to siblings.
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 filtering and default/max limits, but doesn't cover critical aspects like whether this is a read-only operation, potential rate limits, authentication needs, error handling, or response format. For a tool with no annotations, this leaves significant gaps in understanding its behavior.
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 appropriately sized and front-loaded, with a clear purpose statement followed by parameter details in a structured 'Args:' section. Every sentence adds value, though the formatting is basic and could be more polished for readability.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and parameters but lacks behavioral context, usage guidelines, and output details. Without annotations or output schema, more information on response structure or error cases would improve completeness.
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 description adds meaningful semantics beyond the input schema, which has 0% description coverage. It explains that 'signal' accepts values 'long' (bullish), 'short' (bearish), or 'neutral', and specifies 'limit' defaults to 10 with a max of 100. This compensates well for the schema's lack of descriptions, though it doesn't detail data types or constraints beyond what's implied.
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 news filtered by trading signal type.' It specifies the verb ('Get'), resource ('news'), and filtering criteria ('by trading signal type'). However, it doesn't explicitly differentiate from siblings like 'get_news_by_engine' or 'search_news_by_coin', which also filter news but by different attributes.
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 multiple sibling tools for news retrieval (e.g., 'get_latest_news', 'search_news', 'get_news_by_source'), the description lacks context on when signal-based filtering is appropriate, prerequisites, or exclusions, leaving the agent to infer usage.
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 default and max values for 'limit' but doesn't disclose other behavioral traits like rate limits, authentication needs, response format, pagination, or error handling. For a search tool with no annotation coverage, this is inadequate.
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 appropriately sized with a clear purpose statement followed by parameter details in a structured 'Args:' section. It's front-loaded and efficient, though the parameter explanations could be slightly more integrated into the flow.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/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 schema coverage, the description is moderately complete. It covers the basic purpose and parameters well but lacks details on behavioral aspects (e.g., response format, errors) and differentiation from siblings, leaving gaps for effective tool 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?
Schema description coverage is 0%, so the description must compensate. It adds meaningful context for both parameters: 'coin' is explained with examples (e.g., 'BTC', 'ETH'), and 'limit' specifies default (10) and max (100) values. This significantly enhances understanding beyond the bare 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 as 'Search news related to a specific cryptocurrency coin/token,' which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'search_news' or 'search_news_advanced,' which appear to be similar news search functions.
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 like 'search_news' or 'search_news_advanced' from the sibling list. It only states what the tool does without context about its specific use case compared to other news search tools.
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?
With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the tool performs 'search' (implying read-only), it doesn't address important behavioral aspects like rate limits, authentication requirements, response format, pagination, or error handling. The parameter documentation provides some operational context but doesn't constitute comprehensive behavioral transparency.
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 appropriately sized and well-structured with a clear purpose statement followed by detailed parameter documentation. While efficient, the 'Args:' section could be more integrated with the main description rather than appearing as separate documentation. Every sentence adds value, with no redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 5-parameter search tool with no annotations and no output schema, the description provides excellent parameter documentation but lacks important context about the search results format, error conditions, and differentiation from sibling tools. The parameter coverage is comprehensive, but overall completeness is limited by missing behavioral and comparative context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description fully compensates by providing detailed semantics for all 5 parameters. Each parameter gets clear explanations including examples ('BTC,ETH'), format specifications ('type1:cat1,cat2;type2:cat3'), default values ('default 10'), constraints ('max 100'), and purpose clarification ('If true, only return news that have associated coins').
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 performs 'Advanced news search with multiple filters', which is a specific verb+resource combination. However, it doesn't explicitly distinguish this from sibling tools like 'search_news' or 'search_news_by_coin', which likely offer simpler or more targeted search capabilities.
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. With multiple sibling search tools available (search_news, search_news_by_coin, get_news_by_engine, etc.), there's no indication of what makes this 'advanced' version different or when it's preferable to simpler alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/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 discloses the return format (title, source, link, etc.) and ordering behavior ('newest first'), which is valuable. However, it lacks information about authentication requirements, rate limits, pagination, or error conditions that would be important for a news API tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is perfectly structured and concise: purpose statement first, return format second, parameter documentation third. Every sentence earns its place with zero wasted words, and the information is appropriately front-loaded for quick comprehension.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (news retrieval with multiple sibling alternatives), no annotations, no output schema, and 0% schema description coverage, the description provides adequate basics but lacks important context. It covers purpose, returns, and the single parameter well, but doesn't address authentication, error handling, or differentiation from siblings that would make it complete.
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?
With only 1 parameter and 0% schema description coverage, the description fully compensates by explaining the 'limit' parameter's purpose, default value (10), and maximum (100). This adds crucial meaning beyond what the bare schema provides, though it doesn't explain what happens if the limit exceeds 100 or if invalid values are provided.
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 verb ('Get') and resource ('most recent crypto news articles') with ordering ('newest first'). It distinguishes the tool's purpose from siblings like 'search_news' or 'get_news_by_coin' by focusing on recency without filtering criteria. However, it doesn't explicitly contrast with 'get_high_score_news' which might also return recent articles but with quality filtering.
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 like 'search_news' or 'get_news_by_coin'. With 10 sibling tools including various filtering options, the lack of explicit when-to-use or when-not-to-use context leaves the agent guessing about the appropriate selection criteria.
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 default and max values for 'limit' (10, 100), which is useful behavioral context. However, it doesn't disclose critical traits like whether this is a read-only operation, potential rate limits, authentication needs, error conditions, or what the return format looks like (e.g., list of articles with fields). For a tool with no annotations, this leaves significant gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured and concise. It starts with a clear purpose statement, followed by a usage guideline, then details each parameter with examples and constraints. Every sentence adds value without redundancy, and it's appropriately sized for a 3-parameter tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations and no output schema, the description provides good parameter semantics and usage guidance but lacks behavioral transparency (e.g., return format, error handling). For a tool with 3 parameters and multiple siblings, it's adequate but has clear gaps in completeness, especially around output and operational context.
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?
Schema description coverage is 0%, so the description must compensate. It provides clear semantics for all three parameters: engine_type (with examples like 'news', 'listing'), news_type (with examples like 'Bloomberg', 'Reuters'), and limit (with default and max). This adds substantial meaning beyond the bare schema, though it could benefit from more context on valid values or constraints.
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 news articles from a specific source.' This specifies the verb ('Get') and resource ('news articles') with a qualifier ('from a specific source'). However, it doesn't explicitly differentiate from sibling tools like get_news_by_engine or get_latest_news, which likely have overlapping functionality.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit guidance: 'Use get_news_sources first to see available engine types and news type codes.' This tells the agent when to use this tool (after consulting get_news_sources) and references a specific sibling tool. However, it doesn't explain when to choose this tool over alternatives like get_news_by_engine or search_news, leaving some ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/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. It describes the sorting behavior ('sorted by score descending') and output constraints ('maximum results to return'), which are useful. However, it does not cover aspects like rate limits, authentication needs, error handling, or the format of returned articles, leaving gaps for a tool with no annotation support.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the core purpose in the first sentence, followed by a structured 'Args:' section that efficiently details parameters without redundancy. Every sentence adds value, and there is no wasted text, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 2 parameters, no annotations, and no output schema, the description does a good job covering parameter semantics and basic behavior. However, it lacks details on return values (e.g., article fields), error cases, or performance considerations, which would be needed for full completeness in this context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 0%, so the description must fully compensate. It provides clear semantics for both parameters: min_score ('Minimum score threshold') with a default value, and limit ('Maximum results to return') with default and max values. This adds essential meaning beyond the bare schema, effectively documenting all parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action ('Get highly-rated news articles'), identifies the resource ('news articles'), and specifies the rating mechanism ('by AI score') and sorting order ('sorted by score descending'). This distinguishes it from siblings like get_latest_news (which likely sorts by time) or search_news (which likely filters by keywords).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for retrieving high-scoring articles, but does not explicitly state when to use this tool versus alternatives like get_latest_news or search_news. It provides default values and limits, which offer some contextual guidance, but lacks explicit comparisons or exclusions for sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses key behavioral traits: WebSocket connection, real-time updates, duration-based collection (wait_seconds), and filtering capabilities. However, it lacks details on error handling, connection stability, or authentication needs, which are important for a WebSocket tool.
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 well-structured with a purpose statement followed by a bullet-point list of parameters. It is front-loaded with the main action and avoids unnecessary details. However, the parameter list could be more integrated into the narrative for slightly better flow.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations and no output schema, the description covers the tool's purpose and parameters well but lacks details on return values, error cases, or WebSocket-specific behaviors like connection handling. For a real-time subscription tool with 5 parameters, this leaves some gaps in completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It provides clear semantics for all 5 parameters: wait_seconds (duration to listen), max_items (limit on collected items), coins (filter by symbols), engine_types (filter format), and has_coin (boolean filter). This adds significant meaning beyond the basic schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/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: 'Subscribe to real-time news updates via WebSocket' with specific actions like 'connects to the WebSocket feed, subscribes to news with optional filters, and collects incoming messages'. It distinguishes from sibling tools (e.g., get_latest_news, search_news) by emphasizing real-time subscription via WebSocket rather than one-time retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for real-time news updates with filtering, but does not explicitly state when to use this tool versus alternatives like get_latest_news or search_news. It provides context for real-time collection but lacks explicit exclusions or named alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It describes the return format ('flat list of news source codes') which is helpful, but doesn't mention potential limitations like rate limits, authentication requirements, or whether the list is static or dynamic. It adequately describes the basic behavior but lacks operational context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise (two sentences) with zero wasted words. The first sentence states the purpose, the second explains the return format and usage context. Every sentence earns its place and the information is front-loaded appropriately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple zero-parameter lookup tool with no output schema, the description provides sufficient context: purpose, return format, and usage relationship to another tool. It could potentially mention whether the list changes frequently or if there are known limitations, but given the tool's simplicity, the description is reasonably complete.
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 zero parameters, and schema description coverage is 100%. The description correctly indicates no parameters are needed ('List all available...') and provides context about what the tool returns. For a zero-parameter tool with complete schema coverage, this meets the baseline expectation of 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('List') and resource ('all available news type codes'), and explicitly distinguishes this tool from its sibling 'search_news' by explaining its output is used as input for that sibling's 'newsType' parameter. This provides specific differentiation from other news-related tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool: 'for filtering' and specifically 'that can be used with the newsType parameter in search_news.' It provides clear guidance about its relationship to an alternative tool (search_news) and its intended purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/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. It describes the return format ('tree structure with engine types... and their sub-categories'), which is helpful. However, it doesn't mention potential limitations like rate limits, authentication needs, or data freshness. Since annotations are absent, a 4 reflects good but not exhaustive behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured and concise: three sentences that efficiently cover purpose, output format, and usage guidelines. Each sentence adds value without redundancy, and key information is front-loaded. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (simple catalog with 0 parameters), no annotations, and no output schema, the description is mostly complete. It explains the purpose, output structure, and usage context. However, it lacks details on error handling or exact return format specifics, which could be useful for an agent. Still, it's adequate for a low-complexity tool.
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, and schema description coverage is 100% (though schema is empty). The description doesn't need to explain parameters, but it implicitly confirms no inputs are required by not mentioning any. Baseline for 0 parameters is 4, as the description appropriately focuses on output and usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/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 all available news source categories and their metadata.' It specifies the verb ('Get'), resource ('news source categories and their metadata'), and distinguishes from siblings by focusing on cataloging sources rather than retrieving or searching news content. The mention of 'tree structure' and engine types provides additional specificity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool: 'Use this first to understand what news sources are available before searching.' This provides clear guidance on its role as a prerequisite for other news-related tools, distinguishing it from siblings like search_news or get_latest_news that retrieve actual news content.
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:

[![opennews-mcp MCP server](https://glama.ai/mcp/servers/6551Team/opennews-mcp/badges/card.svg)](https://glama.ai/mcp/servers/6551Team/opennews-mcp)

Score Badge

Copy to your README.md:

[![opennews-mcp MCP server](https://glama.ai/mcp/servers/6551Team/opennews-mcp/badges/score.svg)](https://glama.ai/mcp/servers/6551Team/opennews-mcp)

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/6551Team/opennews-mcp'

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