Skip to main content
Glama

zdf_news_by_topic

Fetch ZDF heute news by topic (politik, wissen, or kultur) and limit results to 1-50, with 10 as default.

Instructions

ZDF heute news by topic. topic: politik, wissen or kultur. 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": "zdf_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 disclosure burden. It does give the enforced constraint set (three valid topics, limit range 1..50 with default 10), which is genuinely useful behavior information, but says nothing about ordering, freshness, or what happens on an invalid topic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two terse lines, front-loaded with purpose followed by parameter constraints. Every clause carries information and there is no filler.

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?

With an output schema present, return shape need not be explained, and both input parameters are effectively documented in the description despite zero schema coverage. The remaining gap is a brief note on what a result item represents (headline list vs. full articles) and invalid-input behavior.

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

Parameters3/5

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

Schema coverage is 0% — the schema gives only bare types with no descriptions or enum — so the description must compensate, which it partly does by listing the three valid topic strings and the limit bounds. It stops short of saying whether topic matching is case-sensitive or what an unrecognized topic yields.

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 pair (news by topic, scoped to ZDF heute) and names the domain of topics it returns. It is distinguishable from siblings like zdf_get_article or zdf_search_news by the word 'topic', though it never explicitly contrasts itself with them.

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: enumerating politik, wissen and kultur signals that this is the tool for browsing a themed feed. There is no statement of when to prefer it over zdf_search_news or zdf_headlines, and no prerequisites or exclusions are given.

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