Skip to main content
Glama

zeit_news_by_section

Retrieve articles from a specified DIE ZEIT section in feed order, with an adjustable limit, to collect section-specific news for summaries, monitoring, or research.

Instructions

Newest news of one DIE ZEIT section, in feed order. section: "politik", "wirtschaft", "gesellschaft", "digital", "sport", "gesundheit", "arbeit", "wissenschaft", "zeit-magazin" or "hamburg" (German names work too, e.g. "Wirtschaft"). 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": {
      "section": "<section>"
    },
    "name": "zeit_news_by_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sectionYes

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?

With no annotations, the description carries the full burden. It does add real behavioral detail beyond the schema: ordering ('feed order'), the accepted section vocabulary, and the limit bounds and default. It omits permission/auth expectations, error behavior for an unknown section, and whether results are paginated, so the disclosure is partial rather than complete.

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?

Purpose is front-loaded in the first clause, followed by parameter guidance in the order an agent needs it. The section list is long but earns its place because the schema provides no enum. Slightly awkward line break mid-sentence, but no filler wording.

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, read-style lookup with an output schema (so return shape need not be described), the definition covers everything needed to invoke it correctly. Remaining gaps are marginal: error handling for an unrecognized section and whether results are capped or paginated beyond the limit.

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 it largely does: it enumerates the nine valid section slugs, notes that German/capitalized names like 'Wirtschaft' also work, and specifies limit range 1..50 with default 10. The schema itself has no enum or min/max constraints, so this text is the only source of those semantics. Minor gap: no statement of what happens with an invalid or unknown section.

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: 'Newest news of one DIE ZEIT section, in feed order.' The phrase 'one ... section' implicitly contrasts with the all-sections sibling, and 'newest ... in feed order' distinguishes it from search-style siblings. It never names an alternative explicitly, so differentiation is inferred rather than stated.

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 implied: fetch the latest items from a single section. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. versus zeit_headlines or zeit_search_news), so the agent must infer routing from the sibling names alone.

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