deutschlandfunk-mcp

dlf_get_article

Fetch the full text of a Deutschlandfunk article by providing its URL; news-flash pages may return only the leader text.

Instructions

Full text of one Deutschlandfunk article. url: a deutschlandfunk.de article link, e.g. https://www.deutschlandfunk.de/klimawandel-...-100.html (news-flash pages may return only the leader 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": "dlf_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

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 burden. It does disclose a real behavioral caveat — news-flash pages may return only the leader text — which is valuable and non-obvious. However, it says nothing about permissions, rate limits, or failure behavior for invalid URLs, and 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?

Very short and front-loaded, with the core purpose in the first clause and the caveat last. The awkward mid-sentence line break in the source text is a minor formatting blemish but no content is wasted.

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 single-parameter read tool with an output schema, the description covers purpose, the URL format, and the main edge case (news-flash pages). Only the absence of guidance on obtaining valid URLs or handling errors keeps it from being fully complete.

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: it defines url as a deutschlandlohnfunk.de article link and gives a concrete example format. It does not clarify whether non-DLF or redirect URLs are accepted, keeping it below 5.

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 resource and operation: 'Full text of one Deutschlandlohnfunk article.' An agent can distinguish this from siblings like dlf_search_news or dlf_latest_news, which return lists rather than a single article's body. It stops short of explicitly naming a sibling, so it lands at 4 rather than 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 only implied: the tool takes an article URL, so the agent infers it is for fetching a known article rather than discovering one. No explicit when-to-use/when-not guidance or named alternative (e.g. use dlf_search_news to find URLs first) is given.

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

Deploy Server