dw-mcp

dw_get_article

Retrieves the full text of a Deutsche Welle article from its URL for reading or processing. Use dw.com article links; live blogs and video pages may return little or no body text.

Instructions

Full text of one DW article. url: a dw.com article link, e.g. https://www.dw.com/en/.../a-12345678 (live blogs and video pages may return little or no body text).

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

Input Schema

Name	Required	Description	Default
`url`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does deliver a concrete behavioral limitation: live blogs and video pages may return little or no body text, which tells the agent how to interpret empty results. It does not mention pagination, truncation of long articles, or error behavior on invalid URLs, keeping it short of a 5.

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?

Two compact sentences, front-loaded with the outcome (full text) before the parameter details and caveat. The URL example is long but justified given the zero schema coverage; nothing is redundant.

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 read tool with an output schema already defining return values, the description covers purpose, the required input format, and the main failure mode. Minor gaps (behavior on invalid/non-article URLs, whether body text is truncated) remain but are not blocking.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema only names the property 'Url' with no description, so the description must compensate — and it does, specifying a dw.com article link with a concrete format example including the 'a-12345678' ID pattern. This adds meaning the schema does not provide.

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: returns the full text of a single DW article. This implicitly separates it from the list-oriented siblings (dw_headlines, dw_search_news, dw_latest_articles), 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 implied by the tool's nature (fetch one article body given a URL), and the parenthetical warns that live blogs and video pages may return little or no body text — useful scoping. There is no explicit guidance on when to choose this over dw_search_news or how to obtain the URL in the first place.

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

Deploy Server