Skip to main content
Glama
welt-mcp

welt-mcp

welt_get_article

Fetch the full text of a WELT article from its URL, including title, author, publish time, body, and word count; paywalled or teaser-only pages return only available teaser text.

Instructions

Full text of one WELT article page (JSON-LD articleBody). url: a www.welt.de article URL (containing /article or /plus), e.g. from welt_headlines. Returns title, author, publish time, the body text and its word count. For WELT+ (premium) articles only the teaser is freely available: paywalled=true and body holds the teaser. Short agency flashes can be teaser-only too (teaser_only=true, paywalled=false) — the teaser is then the whole freely available text. Nothing is ever fabricated.

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": {
      "url": "<url>"
    },
    "name": "welt_get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 well: it discloses paywall behavior (paywalled=true, body holds only the teaser), the teaser_only=true case for agency flashes, and guarantees nothing is fabricated. It does not cover failure behavior for malformed or non-article URLs, or any rate/access limits.

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?

The purpose and return shape are front-loaded, followed by the parameter constraint, then the edge cases. Dense and largely waste-free; the paywall/teaser explanation is a touch repetitive but each part adds distinct meaning.

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 one-parameter fetch tool with an output schema, this covers what an agent needs: what it returns, how to form the URL, and how to interpret paywalled/teaser-only results. Only error-handling expectations are missing.

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%, but the single `url` parameter is explained well beyond the schema: domain, required path segment (/article or /plus), and a concrete source example. It lacks a canonical URL form example or note on query strings/locale prefixes.

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?

"Full text of one WELT article page (JSON-LD articleBody)" gives a concrete verb (fetch full text), a specific resource (a single article page), and the extraction source. The reference to welt_headlines as the URL origin implicitly separates this fetch tool from the listing/search siblings, though the distinction is not stated outright.

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?

It states the precondition clearly: the url must be a www.welt.de article URL containing /article or /plus, and points to welt_headlines as a way to obtain one. There is no explicit "do not use this for search/listing" exclusion, so the when-not guidance is left implied.

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