Skip to main content
Glama
Sign In

Currents

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search News

search_news
Read-onlyIdempotent

Search global news by keyword across Currents (70k+ sources). Filter by language, category, country, and date range. Example: search_news({ keywords: "artificial intelligence", language: "en", limit: 15 })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 15,
      "keywords": "artificial intelligence",
      "language": "en"
    },
    "name": "search_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax number of articles to return (default 15).
_apiKeyNoOptional Currents API key. Omit to use the platform key.
countryNoOptional two-letter country code, e.g. "US", "GB", "FR".
categoryNoOptional category filter, e.g. "technology", "business". Use list_categories to see options.
end_dateNoOptional ISO 8601 end of date range, e.g. "2026-02-01T00:00:00".
keywordsYesSearch query, e.g. "climate change", "artificial intelligence".
languageNoTwo-letter language code, e.g. "en", "es", "fr". Default "en".
start_dateNoOptional ISO 8601 start of date range, e.g. "2026-01-01T00:00:00".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "keywords": "artificial intelligence",
+    "language": "en",
+    "limit": 15
+  },
+  {
+    "country": "US",
+    "end_date": "2026-02-01T00:00:00",
+    "keywords": "climate change",
+    "language": "en",
+    "limit": 10,
+    "start_date": "2026-01-01T00:00:00"
+  }
+]
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds the source ('Currents with 70k+ sources') and an example, but does not disclose behavioral details beyond what annotations provide (e.g., rate limits, response structure). It adds marginal value.

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 two sentences plus an example, with no superfluous words. The first sentence states the core purpose, the second lists filters, and the example illustrates usage. Every part earns its place.

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?

The tool has 8 parameters and no output schema, so the description should hint at the return format. It mentions 'Search global news' but does not describe what is returned (e.g., article titles, links, snippets). For a search tool, this is a notable omission. However, it does cover the source and filtering options adequately.

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%, so the schema already documents all parameters. The description lists filters (language, category, country, date range) and gives an example, but adds no new meaning or constraints beyond the schema. Baseline 3 is appropriate.

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 'Search' and the resource 'global news' across 'Currents (70k+ sources)'. It specifies filtering options (language, category, country, date range) and provides an example, making the purpose unambiguous. This distinguishes it from siblings like 'latest_news' which likely returns recent headlines without keyword search.

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 keyword-based news search with filters but does not explicitly state when to use this tool over alternatives like 'latest_news' or 'list_categories'. No when-not or exclusions are provided. The example helps but lacks comparative guidance.

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

All Currents 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