agentsvc.io

News Search

news_search

Read-only

News search: latest news articles and headlines by keyword with title, url, source and published_at from our own index of about 100,000 English web articles a day (built from the GDELT Project, thousands of outlets, last 7 days, updated every 15 minutes) plus Hacker News. Category (business, tech, health, science, politics) filters by GDELT topic. Use for current events and topic monitoring. For crypto news use crypto-news, for what people say about a topic discussion-search, and for full article text pass the URLs to web-read-batch. Params: query (required), limit (max 30), category. Price: $0.0065 USDC per call, paid inside this MCP call via x402 (USDC on Base, Solana, Polygon or Arbitrum). x402 MCP clients such as @x402/mcp pay automatically. Free sample: call with the example input {"query":"AI agents","limit":5}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "news_search"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of articles to return (default: 10, max: 30)
`query`	Yes	Search query (e.g. 'artificial intelligence', 'climate change 2026', 'Apple earnings')
`category`	No	Topic filter. 'tech' puts Hacker News first; the others narrow the GDELT search to that topic.	general

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

changedInput schema / properties / category / description

Previous value: -"News category filter. 'tech' searches HackerNews for developer/tech news. Others search BBC + general news feeds."New value: +"Topic filter. 'tech' puts Hacker News first; the others narrow the GDELT search to that topic."

First observedOct 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, but the description goes well beyond: data provenance, 7-day window, 15-minute refresh cadence, and critically the payment model ($0.0065 USDC via x402 on four chains, auto-paid by x402 clients) plus a free sample call. Pricing and auth are exactly the kind of context the agent cannot infer elsewhere.

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?

Front-loaded with purpose, then alternatives, then params, then price — a logical funnel with no filler sentences. The parenthetical provenance stack is dense but each element (source, size, freshness, refresh rate) is decision-relevant.

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?

No output schema exists, yet the description enumerates the returned fields, defines corpus boundaries and recency, and covers cost and payment mechanics. An agent has everything needed to decide and call 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?

Schema coverage is 100%, so the baseline is 3; the description adds real meaning on top — limit cap of 30 and the non-obvious category behavior ('tech' puts Hacker News first, others narrow the GDELT topic). Only the query syntax stays entirely with the schema example.

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?

States a specific verb and resource ('news search: latest news articles and headlines by keyword') and immediately scopes the corpus: ~100k English articles/day from GDELT plus Hacker News, last 7 days. Returned fields (title, url, source, published_at) are named, so the agent knows exactly what it gets.

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?

Explicit routing rules: 'Use for current events and topic monitoring', with named alternatives — crypto-news for crypto, discussion-search for sentiment, web-read-batch for full text. The when-not cases are stated, not implied.

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

All agentsvc.io tools Inspect

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

Need Help?