Skip to main content
Glama
welt-mcp

welt-mcp

welt_news_by_topic

Fetches WELT news for a chosen topic or feed category in feed order, with a configurable item limit. Filter headlines by subject like Deutschland, Ausland, Fußball, Kultur, or Debatte.

Instructions

Newest WELT news of one topic, in feed order. topic: a feed category such as "Deutschland", "Ausland", "Fußball", "Kultur", "Film", "Debatte" or "Eishockey" (case-insensitive substring match; any category string works). limit: 1..50 (default 10).

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": {
      "topic": "<topic>"
    },
    "name": "welt_news_by_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
topicYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose useful behavior beyond structure: results come in feed order (newest-first) and the limit is bounded 1..50 with a default of 10, but it says nothing about pagination, result volume, or failure behavior on unknown topics.

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?

Compact and front-loaded – the action and ordering come first, then the two parameters in order of importance. Slight redundancy in restating 'topic' twice, but nothing wasteful.

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?

A two-parameter read tool with an output schema, and the description covers both parameters, the ordering, and the default, so an agent can invoke it without guessing. Minor gaps around unknown-topic behavior and result paging keep it from a 5.

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: topic is explained with concrete example categories and the matching rule (case-insensitive substring, any string accepted), and limit is given an explicit range and default. Both parameters gain meaning not present in the bare schema.

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+resource combination: newest WELT news for a single topic, returned in feed order. That is clear and distinguishable from a general search tool, though it never names a sibling to contrast with.

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 by the requirement of a topic category, and the note that 'any category string works' plus case-insensitive substring matching helps the agent know it need not look up an exact category first. However, there is no explicit when-to-use/when-not guidance and no routing toward welt_search_news or welt_headlines for other retrieval needs.

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