Loading ToolBench
MCP server for newsapi.org - provides access to news articles, headlines, and sources from NewsAPI
Three tools with complete input schemas and reasonable descriptions, but significant gaps in parameter documentation and output schema clarity. Tool names lack action verbs (e.g., 'everything' instead of 'search_articles'). Parameter descriptions are present but inconsistent in detail. No documented output schemas, error handling guidance, or recovery paths. Naming conventions do not follow verb_noun pattern, making intent ambiguous for LLMs.
Search through millions of articles from over 80,000 large and small news sources and blogs
Returns information about news publishers available through the API
Returns breaking news headlines for countries, categories, and singular publishers
Tool names lack action verbs. 'everything', 'top-headlines', and 'sources' do not start with verbs (search_, get_, list_). LLMs cannot infer intent from names alone and must read full descriptions, wasting reasoning cycles.
No output schemas documented. Tools return NewsAPI responses but LLMs cannot see field structure, types, or which fields are safe to chain into downstream calls. Baseline: 100% of A+ tools document return types.
Parameter 'ExcludeDomains' uses PascalCase while all others use camelCase. Inconsistent naming invites LLM confusion and parameter mapping errors.
No error handling guidance. Tools do not document what happens on invalid queries, API failures, or rate limits. LLMs have no recovery path if a call fails.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | 2026-07-28+ | v2 |
Parameter descriptions lack actionable constraints. E.g., 'from' and 'to' say 'ISO 8601 format' but do not specify whether time is required, timezone handling, or what happens if dates are invalid.