Skip to main content
Glama
welt-mcp

welt-mcp

welt_search_news

Search WELT news by keyword to find matching headlines and teasers from the RSS feed, with an optional limit on results.

Instructions

Search WELT news by keyword (title + teaser) in the RSS feed. query: free text, e.g. "Bundestag" or "Stromsteuer". limit: 1..50 (default 10). Searches the 30-item feed client-side, newest first, de-duplicated by link.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavioral traits: search is client-side, scoped to a 30-item feed, ordered newest first, and de-duplicated by link. That scoping is valuable and non-obvious. It does not mention permission/auth needs or what an empty result looks like, but the output schema covers return shape.

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 core purpose, then the two parameters stated compactly, then behavioral scoping. Tight and low waste, though the inline parameter narration is slightly cramped and could be split more cleanly.

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?

For a 2-parameter read tool with an output schema, the description covers purpose, both parameters, and the feed-size/dedup constraints that most affect result expectations. Minor gaps remain around no-result behavior and exact matching rules.

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 description coverage is 0%, so the description must compensate, and it does: query is described as free text with concrete examples, and limit is given as a 1..50 range with a default of 10. This adds genuine meaning beyond the bare schema properties, though it omits matching semantics (case sensitivity, partial word matching).

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?

Names a specific verb and resource ("Search WELT news by keyword") and pins down what is searched (title + teaser) and where (the RSS feed), which makes it distinguishable from welt_get_article or welt_headlines in practice. It never names a sibling explicitly, so it falls short of a 5.

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?

Usage is implied rather than stated: the note that it searches only the 30-item feed client-side, newest first, tells an agent when NOT to rely on it for deep/archival search. However, there is no explicit instruction for choosing between this and welt_headlines or welt_get_article.

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