zdf-mcp

zdf_headlines

Retrieve current ZDF heute headlines with an adjustable limit of 1 to 50 results (default 10) for quick news updates.

Instructions

Latest ZDF heute headlines. limit: 1..50 (default 10).

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

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are supplied, so the description bears the full behavioral burden, and it does establish that results are ordered/timely ('Latest') and that the list size is bounded. It says nothing about authorization, caching/refresh cadence, or error behavior when limit is out of range, though for a simple public read endpoint the missing items are modest.

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 short fragments with zero padding, and the resource is front-loaded before the parameter note. The telegraphic style omits a verb, but nothing wastes the agent's reading time.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shape need not be described, and the single optional parameter is covered by the range note. However, with no annotations and no indication of how this differs from topical or search siblings, the definition stops at minimum viable for a list endpoint.

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?

The schema documents only a default of 10 for limit with no description, so the description's 'limit: 1..50 (default 10)' adds genuine constraints (the 1..50 bound) that the schema does not express. It does not say what happens for out-of-range values, which keeps it short of a 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?

The description names a specific resource and recency qualifier ('Latest ZDF heute headlines'), so an agent knows it retrieves current headlines from ZDF. It does not explicitly contrast itself with siblings like zdf_search_news or zdf_news_by_topic, and it uses no verb, so the agent must infer retrieval from the noun phrase.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of alternatives; nothing says whether this is for browsing the current front page versus searching or filtering topically. The word 'Latest' weakly implies 'for current news,' but no exclusion or routing to a sibling is stated.

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

Deploy Server