Skip to main content
Glama

zeit_search_news

Search DIE ZEIT's main news feed by keyword to find relevant articles, returning de-duplicated results in feed order with an adjustable limit.

Instructions

Search DIE ZEIT news by keyword (title + teaser) in the main feed. query: free text, e.g. "Bundestag" or "KI". limit: 1..50 (default 10). Searches the main feed (15 items) client-side, newest first, de-duplicated by link.

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": "zeit_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.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that only a 15-item main feed is scanned, that matching happens client-side, that results are newest first, and that they are de-duplicated by link. It omits auth requirements and empty-result behavior, which would complete the picture.

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?

Three tight sentences, front-loaded with the purpose, then parameter detail, then search mechanics; nothing wasted. The only blemish is an awkward line break splitting 'main feed' mid-phrase.

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?

An output schema exists, so return values need not be explained, and the definition covers corpus breadth, ordering, and de-duplication plus both parameters' semantics. For a two-parameter search tool this is nearly complete, with only empty-result and permission details missing.

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 explain both parameters, and it does: query is described as free text with concrete examples ('Bundestag', 'KI'), and limit is bounded at 1..50 with a default of 10, adding a range the schema lacks. It repeats the default already present in the schema but adds genuine constraint information.

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 ('Search DIE ZEIT news by keyword') and narrows scope to title + teaser in the main feed, which separates it from a broader all-sections search. It stops short of naming the sibling tool it differs from, so the differentiation must be inferred from the words 'main feed'.

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?

Scope ('main feed') implicitly signals when to pick this over an all-sections search, and the 15-item corpus size hints at its limited reach. But there is no explicit when-to-use or when-not-to-use statement and no named alternative.

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