Skip to main content
Glama

zdf_search_news

Search current ZDF heute headlines by keyword or phrase to find recent news items, with an adjustable result limit from 1 to 50 (default 10).

Instructions

Keyword search over the LATEST ZDF heute headlines (the RSS feed holds roughly the last 173 items — this is not a full-archive search). query: keyword or phrase. 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": {
      "query": "<query>"
    },
    "name": "zdf_search_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the important limitation that results come from a rolling window of roughly 173 RSS items rather than an archive, but it says nothing about ordering, update recency, or what a no-match response looks like. Since an output schema exists, the missing return-format detail is somewhat mitigated, but permission and error behavior remain unaddressed.

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?

Three short sentences with the core purpose front-loaded and the scope caveat immediately after it; every sentence contributes information, and the parameter notes are compactly appended without a separate wasteful section.

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 two-parameter search tool with an output schema, this covers what an agent needs: the data window, the parameter meanings, and the result cap. The remaining gap is mainly match behavior for query and result ordering, which are relevant but minor for correct invocation.

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 description coverage is 0%, so the description must compensate and largely does: it defines query as a 'keyword or phrase' and documents limit's bounds (1..50) in addition to the schema's default of 10. The only gap is that match semantics for query (exact phrase vs. tokenized keywords) are left ambiguous.

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 (keyword search over the latest ZDF heute headlines) and bounds the scope explicitly with 'the RSS feed holds roughly the last 173 items — this is not a full-archive search.' It doesn't name a sibling such as zdf_headlines or zdf_get_article to sharpen the distinction, so it stops just short of a 5.

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?

Gives clear context for when the tool applies (latest headlines only) and an explicit exclusion (not a full-archive search), which is genuinely useful routing information. It does not name an alternative tool for archive queries or for browsing without a keyword, so the alternative-selection guidance is incomplete.

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