Skip to main content
Glama
websearch-mcp

websearch-mcp

by xronocode

search_news

Read-onlyIdempotent

Find fresh news and announcements, including launches and tariff or partnership updates, without provider quotas; returns titles, URLs, sources, dates, and engine tags.

Instructions

Free LOCAL news search, no provider quota. Use for fresh announcements, launches, tariff/partnership news. Route: Google News RSS (zero-key) -> Brave news -> ddgs. region optional ('de-de', 'us-en') selects the Google News edition and the ddgs region; empty = auto from the query script. Returns title, URL, source, date and an [engine: ...] tag. Results cached 24h.

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": "search_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
regionNo
max_resultsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, but the description still adds real behavior: no provider quota, a fallback routing chain (Google News RSS zero-key -> Brave news -> ddgs), and 24h result caching. The cache note in particular tells the agent that results may be stale, which the annotations cannot convey.

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 the key differentiator (free, local, no quota), then usage, then mechanics, in four tight lines with no filler. Minor jargon ('ddgs', 'the query script') assumes provider knowledge the agent may not have.

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?

An output schema exists, yet the description still lists title, URL, source, date and the [engine: ...] tag, which is mildly redundant but harmless. The one real gap is max_results, left entirely to the bare schema field for a tool that can return variable numbers of results.

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 0%, so the description carries the parameter burden and it only partially discharges it. It explains region well (format 'de-de'/'us-en', selects both the Google News edition and the ddgs region, empty = auto from the query script) but says nothing about max_results or its default of 8.

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?

States a specific verb and resource ("news search") plus a narrowing scope ("fresh announcements, launches, tariff/partnership news"), which is enough to separate it from the generic search siblings. It stops short of naming which sibling to use instead when the query is not news-related.

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?

"Use for fresh announcements, launches, tariff/partnership news" gives a clear usage context with concrete example intents. There are no explicit exclusions or named alternatives (search, search_semantic), so the agent must infer that non-news or archival queries belong elsewhere.

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

Deploy Server

Other Tools