Skip to main content
Glama
welt-mcp

welt-mcp

welt_headlines

Fetch WELT top headlines from the official RSS feed, newest first, with a configurable limit of 1–50 items.

Instructions

Top headlines from WELT (official RSS feed, 30 items), newest first. limit: 1..50 (default 10). Items carry title, link, teaser, author, category, topic, premium flag (WELT+), subtype (news/video/opinion), image URL and publish time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "welt_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: the source is a 30-item official RSS feed and ordering is newest first. It also enumerates the returned item attributes, though it does not mention error handling or whether limit above 30 is truncated.

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?

Three tight sentences, front-loaded with the resource and source, followed by parameter semantics and payload shape. No filler.

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?

Output schema exists, so item field enumeration is partly redundant, but the parameter range and feed-size cap fill the real gaps. Only truncation behavior at limit>30 is left unstated for a simple one-parameter feed tool.

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 0%, so the description must compensate, and it does: 'limit: 1..50 (default 10)' gives range and default beyond the bare integer schema. It does not state what happens for values above the 30-item feed size, leaving one edge case unresolved.

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 ('Top headlines from WELT') plus scope details: official RSS feed, 30 items, newest first. This separates it from search or topic-filtered siblings implicitly, though no sibling is named explicitly.

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 only implied — an agent can infer this is the default headlines feed, but the description never says when to prefer it over welt_news_by_topic or welt_search_news, nor any exclusions.

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