Skip to main content
Glama

Newsdata

by io.github.pipeworx-io
OverviewDiscussionsAdmin

News Sources

news_sources
Read-onlyIdempotent

List available global news sources. Filter by country (2-letter), category, and language. Returns source id, name, url, category, country, and language — useful for discovering which outlets cover a given region or topic. Example: news_sources({ country: "us", category: "technology" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyNoOptional — your own NewsData.io API key for higher limits; omit to use the shared Pipeworx key.
countryNo2-letter country code to filter sources by, e.g. "us", "gb"
categoryNoNews category to filter sources by, e.g. "business", "technology"
languageNoLanguage code to filter sources by, e.g. "en", "es"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "category": "technology",
+    "country": "us"
+  },
+  {
+    "category": "business",
+    "country": "gb",
+    "language": "en"
+  }
+]
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds return fields and example but doesn't contradict annotations.

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?

Two sentences plus example, no filler. Efficiently conveys purpose, filters, return fields, and usage hint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only listing tool with no output schema, description covers input filters, return fields, and provides an example. Annotations cover behavioral traits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions. Description adds example call and global context, but parameters are already well-documented.

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?

Clearly states 'List available global news sources' with specific verb and resource. Distinguishes from siblings like crypto_news and latest_news.

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?

Describes use case: 'useful for discovering which outlets cover a given region or topic.' No explicit when-not-to-use, but context implies search for sources rather than articles.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Newsdata toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources